Documentation

1---2name: documentation3description: Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.4---5 6# Technical Documentation7 8Write clear, maintainable technical documentation for different audiences and purposes.9 10## Document Types11 12### README13- What this is and why it exists14- Quick start (< 5 minutes to first success)15- Configuration and usage16- Contributing guide17 18### API Documentation19- Endpoint reference with request/response examples20- Authentication and error codes21- Rate limits and pagination22- SDK examples23 24### Runbook25- When to use this runbook26- Prerequisites and access needed27- Step-by-step procedure28- Rollback steps29- Escalation path30 31### Architecture Doc32- Context and goals33- High-level design with diagrams34- Key decisions and trade-offs35- Data flow and integration points36 37### Onboarding Guide38- Environment setup39- Key systems and how they connect40- Common tasks with walkthroughs41- Who to ask for what42 43## Principles44 451. **Write for the reader** — Who is reading this and what do they need?462. **Start with the most useful information** — Don't bury the lede473. **Show, don't tell** — Code examples, commands, screenshots484. **Keep it current** — Outdated docs are worse than no docs495. **Link, don't duplicate** — Reference other docs instead of copying