Run docs like software: pick the tooling by needs (Docusaurus/Mintlify/MkDocs/Starlight), keep docs in the repo with PR review, build/preview/deploy in CI, version docs to match the product, and gate quality with link-checking + example-testing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/technical-writing-docs:docs-as-code-siteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Docusaurus/Starlight (flexible) / Mintlify (hosted, polished) / MkDocs (simple). Not the heaviest for a 20-page site.
Docusaurus/Starlight (flexible) / Mintlify (hosted, polished) / MkDocs (simple). Not the heaviest for a 20-page site.
Docs in the repo, reviewed in PRs, build + preview per PR, deploy on merge (with devops-cicd). A separate wiki rots.
Link-checking + example-testing in CI fail the build on broken links/snippets.
Docs versioned to product versions; archive old, don't silently overwrite. Good search/IA beats more pages.
npx claudepluginhub mcorbett51090/ravenclaude --plugin technical-writing-docsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.