What problem does it solve? Teams struggle to choose the right API documentation renderer, keep OpenAPI specs enriched with examples, generate client SDKs, and communicate breaking changes without breaking consumer trust. This Skill encodes the complete decision-making and execution playbook for turning a raw OpenAPI spec into a published developer experience. ## Core Features & Use Cases - Renderer Selection: Compares Scalar, Redoc, Swagger UI, Mintlify, Stoplight, and Bump.sh with a decision tree and migration cost estimates. - Spec Enrichment & Deployment: Guides JSON example authoring (inline, named, x-codeSamples, overlays) and deployment to GitHub Pages, Netlify, Vercel, or self-hosted Docker. - SDK Generation & Changelog Discipline: Covers openapi-generator-cli, Fern, and Speakeasy for TypeScript/Python/Go, plus the [BREAKING] changelog convention with Bump.sh CI diff gates. - Use Case: Given an existing openapi.yaml, select Scalar as the renderer, deploy it to GitHub Pages via a GitHub Actions workflow, generate a TypeScript SDK, and write a compliant changelog entry for a breaking endpoint rename. ## Quick Start Ask the assistant to set up API documentation for your OpenAPI spec, for example by saying: set up Scalar docs for my openapi.yaml and deploy them to GitHub Pages.