docslisted

# docs Documentation a developer can hand-verify against the source: every claim anchored to a real file path, every non-obvious decision explained, every rejected alternative recorded. Renders as a docsify site by default — plain markdown that also reads correctly on GitHub. ## Invocation `/docs` invokes this skill by name, and `--docs` fires it through the hook — both are the same request. Bare, either means *document what we just worked on*: infer the target from the conversation — the files touched this session, the feature just built — and say what you picked before writing. With an argument (`--docs auth`, `--docs the map module`) that's the target. **`--adopt` also invokes this** when it finds a project with no documentation at all, wanting Scaffold mode and the overview page — not a full site. It confers its own grant, which is commit and not push, so what gets scaffolded there may be committed even though this flag alone authorizes nothing. **`--tools` invokes this too**, handing over `record.tooling.catalog` for you to adapt into a **Claude tooling** annex page (T11). The catalog is the source and stays that skill's; the page is yours — its wording, its placement, and its index and sidebar rows. Re-render its interaction diagram for this site's renderer under `references/style-guide.md`'s three rules rather than reshaping it by hand. Adapt what you are given and **do not invent edges the catalog does not claim**: you are rendering someone else's facts, and this