# docs/

Project documentation for AI-driven development. Each subfolder has a single, narrow purpose. Keep files in the right folder so Claude can find them by convention.

## Subfolders

### `prd/`

Product Requirements Documents. AI-driven PRDs produced by `skills/ai-driven-prd/` or hand-written.

**Naming:** `prd-v<MAJOR>.<MINOR>.md` — e.g. `prd-v0.1.md`, `prd-v1.0.md`. One file per product version.

### `plans/`

Development plans, one per requirement (or coherent batch of requirements). Generated by `skills/generate-dev-plan/` or written by hand.

**Naming:** `<REQUIREMENT_ID>.md` — e.g. `FR-001.md`, `FR-AUTH-003.md`.

**Format:** every task is a markdown checkbox. Mark `[ ]` → `[x]` as work completes.

```markdown
- [ ] FR-001.1 — Build login form component
- [x] FR-001.2 — Wire form to /api/auth/login
- [ ] FR-001.3 — Handle 401 response with inline error
```

### `designs/`

UI designs exported from Stitch, Claude Design, or another tool. Both the HTML export and a screenshot.

**Naming:** `<REQUIREMENT_ID>-<slug>.{html,png}` — e.g. `FR-001-login.html`, `FR-001-login.png`. Open the HTML to understand the target UI before implementing the requirement.

## Adding more

Anything that doesn't fit the three categories above (architecture notes, ADRs, runbooks, glossary) lives at the root of `docs/`. Reference it from `CLAUDE.md` via `@docs/<file>.md` only if Claude needs it during regular sessions; otherwise leave it as on-demand documentation.