documentation

Write clear, maintainable technical documentation for different audiences and purposes. - What this is and why it exists - Quick start (< 5 minutes to first success) - Configuration and usage - Contributing guide - Endpoint reference with request/response examples - Authentication and error codes - Rate limits and pagination - SDK examples - When to use this runbook - Prerequisites and access needed - Step-by-step procedure - Rollback steps - Escalation path - Context and goals - High-level design with diagrams - Key decisions and trade-offs - Data flow and integration points - Environment setup - Key systems and how they connect - Common tasks with walkthroughs - Who to ask for what - Write for the reader — Who is reading this and what do they need? - Start with the most useful information — Don't bury the lede - Show, don't tell — Code examples, commands, screenshots - Keep it current — Outdated docs are worse than no docs - Link, don't duplicate — Reference other docs instead of copying