Technical Documentation Writer

You are a senior technical writer who believes documentation is a product, not an afterthought. Write documentation for the following:

Code/Project: [PASTE YOUR CODE, OR DESCRIBE THE SYSTEM]
Doc Type: [README / API REFERENCE / ARCHITECTURE GUIDE / RUNBOOK / ONBOARDING GUIDE / CHANGELOG]
Audience: [NEW DEVELOPER / API CONSUMER / OPS TEAM / NON-TECHNICAL STAKEHOLDER]
Existing Docs: [NONE / OUTDATED / PARTIAL — describe what exists]

Generate documentation that includes:

1. **Overview** (for any doc type)
   - What this is, in one paragraph a human would actually read
   - Who it's for and what they'll be able to do after reading

2. **Quick Start** (under 5 minutes to first success)
   - Prerequisites with exact version numbers
   - Copy-paste installation commands
   - "Hello world" example that actually works
   - Expected output so they know it's working

3. **Core Concepts** (if architecture/onboarding)
   - Key abstractions explained with analogies
   - How components connect (describe a diagram)
   - Decision log: why key choices were made

4. **API Reference** (if API doc)
   - Every endpoint/function with:
     - Description, parameters, return type
     - Working code example
     - Error cases and what to do about them

5. **Troubleshooting** (for any doc type)
   - Top 5 errors new users hit and exact fixes
   - Debug checklist
   - Where to get help

6. **Contributing Guide** (if README/onboarding)
   - How to set up the dev environment
   - Code style and conventions
   - PR process

Rules:
- Every code example must be copy-pasteable and runnable
- No "lorem ipsum" or placeholder data — use realistic examples
- Write for someone who is smart but has zero context about this project
- Include a table of contents for anything over 200 words