What problem does it solve? Developer guides for SDKs, libraries, CLIs, frameworks, and API platforms often fail readers: no clear starting point, hello-world examples that never reach real value, fabricated endpoints, and samples that go stale when the tool ships a new version. This Skill provides the method and quality bar for authoring (or amending) a developer guide that takes a reader from install to a verified first success and on to a correct production integration. ## Core Features & Use Cases - Method-driven authoring: Organizes the guide around developer goals rather than endpoints, enforces concepts-before-recipes, correctly typed Diataxis modes (tutorial, how-to, explanation, reference), and a signposted start-here with a fast, verifiable first call. - Grounded, never fabricated content: Drives recipes and code samples off the handed-in feature-spec and api-reference, surfaces missing upstreams as explicit assumptions, and links into the API reference instead of duplicating it. - Versioned amend workflow: Edits an existing guide in place when the tool changes, sweeping every sample and recipe for stale references, bumping the guide's own version, and marking superseded content. - Use Case: Given a feature-spec and api-reference for a payments SDK, produce a guide with a runnable getting-started (env-var credentials, sandbox first call, expected output), goal-named integration recipes, an end-to-end tutorial, production best-practices (retries, idempotency, pagination, webhooks), and a troubleshooting path. ## Quick Start Use authoring-developer-guide to turn the attached feature-spec and api-reference into a developer guide for our SDK.
