| name | api-docs-stinger |
| description | API documentation authority — Swagger UI / Redoc / Scalar / Mintlify / Stoplight / Bump.sh tool selection, OpenAPI spec enrichment with JSON examples, self-hosted and managed hosting, SDK generation (TypeScript / Python / Go via openapi-generator-cli and Fern/Speakeasy), and changelog discipline. Invoke when the user says "set up API docs", "which docs renderer should I use", "generate an SDK from my spec", "deploy my OpenAPI docs", "write an API changelog", "compare Redoc vs Scalar", or "publish API reference to GitHub Pages". Do NOT invoke for general documentation sites (library-worker-bee), API security scheme audits (security-worker-bee), or backend route design (python-worker-bee / react-worker-bee). |
api-docs-stinger
Procedural arsenal for api-docs-worker-bee, the Legion AI Tools Factory's API documentation specialist. This stinger encodes the tool comparison matrix, the example-authoring discipline, the deployment playbooks for all major hosting targets, the SDK generation pipelines, and the changelog discipline that keeps API consumers informed without breaking them.
When this stinger applies
Load this stinger when api-docs-worker-bee is invoked. Typical triggers:
- "Set up API docs for this project."
- "Which renderer should I use — Redoc or Scalar?"
- "Deploy my OpenAPI spec to GitHub Pages."
- "Generate a TypeScript SDK from my spec."
- "Write a changelog entry for this breaking API change."
- "Audit our existing API docs."
- "Add examples to every endpoint."
Do NOT load it for:
- Full documentation sites beyond the API reference (route to
library-worker-bee).
- OpenAPI security scheme audits (route to
security-worker-bee).
- REST/GraphQL route design (route to
python-worker-bee or react-worker-bee).
- CI/CD pipeline design for the docs deployment (route to ; this stinger provides the workflow file template but does not architect the full pipeline).
