docslisted

Use when asked to generate, update, or refresh a codebase's architecture reference docs (DESIGN.md plus docs/capstone/ topic files), map the architecture, or document the data models, typing conventions, and module boundaries so AI sessions read docs instead of re-exploring the repo. Descriptive only; refreshes just the topics whose covered paths changed since their commit stamps.
GentBajko/capstone · ★ 4 · Data & Documents · score 77

Install: claude install-skill GentBajko/capstone

# Capstone: Codebase Architecture Reference Generator Generate or refresh a descriptive architecture reference for the current project: a lean `DESIGN.md` index at the project root plus topic files in `docs/capstone/`. The audience is future Claude sessions — they read these docs instead of re-exploring the repository. **Announce at start:** "I'm using the capstone skill to generate/refresh the architecture reference." ## Phase 0 — Mode select and routing 0. Read `references/core.md` — the hard rules, voice rules, and user config. The config always lives at the fixed path `docs/capstone/capstone.json`, regardless of `docs_dir` (`docs_dir` relocates generated outputs only, never the config). Its keys override the defaults below; `docs_dir` and `index_file` must be relative paths inside the repository. 1. Routing. The reserved subcommand words (`check-docs`, `ask`, `changelog`, `review`, `guides`, `onboarding`, `mockup`, `logic`, `architecture`, `code-prefs`, `stack`, `build`, `groom`, `plan`, `implement`, `implementation`, `start`) each route to `references/protocols/<name>.md` — read `references/core.md` plus that one protocol file and execute it; behaviors live there, not here. **Exception: when this skill was invoked as `docs`, topic names win over subcommand names** — the user already chose docs, so `docs architecture` regenerates `01-architecture.md` and never starts the architecture interview. On the `help` argument, run `