scribekit-docslisted

Write, rewrite, reorganize, or deep-verify documentation for the current project's docs site (MDX), sourced entirely from the project's own code so every documented fact, option, default, and code sample is true. Use when the user wants to create/write/draft/document a new docs/reference/guide page; rewrite/audit/fact-check/update an existing one against the current code; reorganize/restructure/reshuffle the docs as a whole - fix the sidebar, the nav, the tabs, the groups, the ordering, or the information architecture when the structure is a mess, pages sit in the wrong section, or the reading order makes no sense; or deep-verify the WHOLE corpus before a release - verify/validate that every page is still true and up to date against the code and that the docs are ready to ship/release/deploy, fanning out one subagent per page and reporting every issue for the user to pick from (add --scan to only report, without changing anything). Each page's on-brand hero is generated by the companion /scribekit-hero skill
daanvandenbergh/scribekit · ★ 2 · Web & Frontend · score 63

Install: claude install-skill daanvandenbergh/scribekit

# scribekit-docs A portable skill - **one skill, four jobs**: write a documentation page, rewrite (or just audit) a page, reorganize the corpus's structure, and deep-verify the whole corpus before a release, for the docs site of whatever project it is dropped into. **Nothing about any project is baked in.** It **learns the current project first** (Step 0), then writes and rewrites to match it. The one way it differs from the [/scribekit-blog](../scribekit-blog/SKILL.md) blog writer is decisive: **docs are project-dedicated, so the primary source is this project's own code, not the open web** - every fact, option, default, and code sample is traced to real source, never recalled from memory. Each page's **hero image** is produced by the companion **[/scribekit-hero](../scribekit-hero/SKILL.md)** skill (`docs-hero`) - the `write` flow calls it automatically. This file is the router. ## Step 0 - Learn this project (every mode starts here) Before anything else, discover the project so voice, structure, and frontmatter are *this project's*, not generic. Gather and keep as working notes for the run: - **Identity, voice, routes** - read `CLAUDE.md` / `AGENTS.md` / `README`, skim the landing page, and open the 1-2 strongest existing docs pages: that voice and formatting is your calibration target. Note the project's own conventions (its `CLAUDE.md`): indentation, punctuation (some projects ban em-dashes - this one does), British vs US spelling. - **Find the `Docs` wiring**