docs

# Docs Keep `./docs/` honest. Scout the code, diff it against what the docs claim, write what's true. Small canonical set - easy to keep current, hard to let rot. ## Two surfaces, one skill `./docs/` is **team-facing** truth - journals are personal (injected `Journals:` path), plans and reports live at the injected `Plans:` / `Reports:` paths, never in `./docs/`. `init`/`update`/`check`/`adr` own internal Markdown; `site` owns the rendered public website (formerly the separate tech-docs skill). Internal-content hard rules 1-5 below apply to the Markdown surface; the site surface carries its own rules in `references/site-workflow.md`. Rules 6-7 (unslop + prose standard) apply to both. ## Subcommands | Subcommand | Reference | When | |---|---|---| | `init` | `references/init-workflow.md` | Fresh repo - no `./docs/` yet, or only a stub README | | `update` | `references/update-workflow.md` | Code drifted from docs after a feature, refactor, or migration | | `check` | `references/check-workflow.md` | Validate-only: required files, size, freshness, broken refs. No writes. | | `adr` | `references/adr-workflow.md` | Record an architecture decision (the *why* behind an irreversible choice) under `docs/decisions/` | | `site` | `references/site-workflow.md` | The rendered public docs website (Astro Starlight): create, modernize, validate, ship. Owns `assets/theme.css` (centered profile) and `references/site-blueprint.md` | Parse `$ARGUMENTS` first word (runtimes without `$ARGUMENT...