Developer Documentation Writer

This skill takes what you know about your API or system and turns it into documentation structured the way developers actually read: task-first. You provide your API surface, endpoint behaviors, or system concepts; your target developer persona; and the top errors or sticking points your users hit. The skill returns an API reference organized around developer goals, a quickstart built to reach a working example fast, and a troubleshooting section grounded in real failure modes — not theoretical ones.

A realistic input looks like this: a webhook-based payment API whose existing docs are a flat list of endpoints, a target persona of backend engineers integrating for the first time, and three common points of confusion — authentication header format, idempotency key behavior, and handling retry payloads. The skill reorganizes the reference around integration tasks, writes a quickstart that ends with a verified test transaction, and produces a troubleshooting section with the exact error codes those engineers encounter.

Sample output excerpt — Quickstart section header structure: '1. Get your API key (2 min) — 2. Make your first authenticated request — 3. Handle your first webhook event — 4. Verify end-to-end in test mode.' Each step includes a minimal working code snippet, the expected response, and a single-sentence note on the most common mistake at that step. The reference entries follow the same pattern: goal stated first, parameters second, errors third.