> ## Documentation Index
> Fetch the complete documentation index at: https://vibecoderdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build In Public

> How and why this project is built entirely in the open — code, agents, pipelines, and all.

# Build In Public

Everything about Vibe Coder Docs is open. The code, the agents, the pipelines, the research, the reports — all of it. You can watch it happen in realtime.

## Why Build In Public?

This project exists to help people build better software with AI tools. It would be hypocritical to do that behind closed doors. By building in public, we:

* **Show the process**, not just the result — so you can learn from how we build, not just what we build
* **Stay accountable** — public commitments are harder to abandon
* **Invite contribution** — if you see something wrong or missing, you can fix it
* **Demonstrate the tools** — this entire project is built with the same AI coding tools we're documenting

## What's Open

<CardGroup cols={2}>
  <Card title="Open Source Repo" icon="github">
    All code, configuration, and content lives in the [public GitHub repo](https://github.com/shadowcodex/vibe-coder-docs). Every line of it.
  </Card>

  <Card title="Open Source Agents & Pipelines" icon="robot">
    The agent teams and content pipelines we use to research, draft, and publish documentation are all in the repo. You can run them yourself.
  </Card>

  <Card title="Open Source Research" icon="magnifying-glass">
    Industry research pipelines that scan for CVEs, breaches, AI developments, and emerging threats — all automated and transparent.
  </Card>

  <Card title="Open Source Reports" icon="chart-line">
    Generated reports on industry trends, security incidents, and AI developments are published openly in the [Updates](/updates) section.
  </Card>
</CardGroup>

## Realtime Commits & PRs

Every change to this project goes through Git with full context:

* **Commits** include clear messages explaining *what* changed and *why*
* **Pull requests** include discussion, review comments, and rationale
* **Nothing is squashed or hidden** — the full history is the point

Follow along on the [commit history](https://github.com/shadowcodex/vibe-coder-docs/commits/main) or [watch the repo](https://github.com/shadowcodex/vibe-coder-docs) for notifications.

## Current Priorities

These are the active priorities, in order:

1. Define topics and concept areas
2. Build pipeline for content creation and deployment
3. Focus on security and patterns first
4. Build industry research and report pipeline
5. Grow other topics afterwards
6. Guides and tips for using vibe coding tools better
7. Whatever else comes next

## Current TODOs

* **Pipeline Builder** — Topics + Descriptions + Opinions
* **Pipeline Executor** — Takes topics + context, delegates to agent team to finalize, pushes to human-in-the-loop queue for approval/modification
* **Agent Team** — Defined agent teams for specific areas and topic concepts, orchestrated by Claude Code
* **Industry Research Pipeline** — Find most recent industry information on AI/LLM/Agentic, source into reports for discovery and learning, publish reports
* **Industry Fails Pipeline** — Find most recent CVEs, breaches, and incidents, ensure there are topics that cover them, flag gaps for pipeline inclusion

<Note>
  These priorities and TODOs are also tracked in the [README](https://github.com/shadowcodex/vibe-coder-docs/blob/main/README.md) and will evolve as the project grows.
</Note>