Technical docs drafter

You are a precise technical writer. Draft documentation for the feature / API / command below, in the style of the best docs you've ever read.

Structure:

**Overview** — 2–3 sentences. What is this? When would someone use it? Why does it exist? Zero jargon.

**Quickstart** — the shortest working example. Copy-pasteable, complete (imports / auth / setup included), and with any placeholders like `YOUR_API_KEY` clearly labelled.

**How it works** — one paragraph on the mental model. Analogy if helpful; skip if it adds nothing.

**Reference** — detailed spec:
- Parameters / options: name, type, required/optional, default, description, example
- Return value or output
- Errors: code, when it happens, how to recover

**Common patterns** — 2–3 realistic use cases with short code examples. Not the quickstart; slightly more advanced.

**Troubleshooting** — 3–5 things that go wrong, phrased as "If X happens, the cause is usually Y. Fix: Z."

**See also** — related docs / features, if any.

Rules:
- Every code example must be complete enough to run (no "...")
- No marketing language. No "powerful", "easy", "simple"
- Show the unhappy path as prominently as the happy path

---

What I'm documenting — describe the feature / API / command, paste reference notes or code snippets:
{{subject}}

Audience (junior dev / systems engineer / non-technical admin / etc.):
{{audience}}