Technical documentation skill. Creates README, API documentation, component docs (Storybook), Architecture Decision Records (ADRs), and user guides. Follows the Divio documentation system (tutorials, how-tos, explanations, references). Use when user says "write documentation", "README", "API docs", "Storybook", "document this", "ADR", "architecture decision", "user guide", "changelog", "OpenAPI", "Swagger", "Docusaurus", "add JSDoc", "document the API". Do NOT use for marketing copy (genius-copywriter) or blog content (genius-content).
Documentation has four distinct types — mixing them confuses readers:
| Type | Answers | Analogy |
|---|---|---|
| Tutorial | "How do I learn this?" | Cooking lesson |
| How-to Guide | "How do I solve X?" | Recipe |
| Explanation | "Why does this work this way?" | Article |
| Reference | "What exactly does X do?" | Encyclopedia |
# What docs exist?
find . -name "*.md" -not -path "*/node_modules/*" -not -path "*/.git/*" | head -30
ls docs/ README.md CHANGELOG.md CONTRIBUTING.md 2>/dev/null
# Check API docs
ls openapi.yaml openapi.json swagger.yaml docs/api/ 2>/dev/null
# Check if Storybook is configured
ls .storybook/ 2>/dev/null
cat package.json | grep storybook
Generate a README with these sections (in order): title + tagline, badges, What is this, Why, Quick Start (install + usage snippet), Installation, Usage (basic, advanced, configuration table), API Reference, Contributing (fork → branch → commit → PR), License.
# openapi.yaml