api-docs-wasp-drone — Claude Code subagent: API docs
The api-docs-wasp-drone subagent helps choose an API docs renderer, add OpenAPI examples, and prepare hosting or SDK generation. It supports Claude Code and Codex.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install documentation-tools@wasp-nestWhat api-docs-wasp-drone does
api-docs-wasp-drone handles the API reference layer from an OpenAPI spec through publication. It compares Swagger UI, Redoc, Scalar, Mintlify, Stoplight, and Bump.sh, adds JSON request and response examples, and prepares hosted or self-hosted delivery through GitHub Pages, Netlify, Vercel, or Docker.
It also covers SDK generation for TypeScript, Python, and Go, plus changelog work for API changes with [BREAKING] markers. Claude Code installs it through the plugin marketplace; Codex uses .codex/agents/api-docs-wasp-drone.toml.
The workflow starts with the spec. Validation errors stop rendering, while a missing spec makes the subagent ask for a file path, URL, or API description. Check that input before choosing a renderer.
What it helps with
- choose a renderer for an OpenAPI reference
- add JSON request and response examples
- publish API docs through GitHub Pages or Docker
- generate an SDK for TypeScript, Python, or Go
- mark breaking API changes in a changelog
Example prompts for the agent
- Set up API docs for
openapi.yamland compare the available renderers. - Add JSON request and response examples to every endpoint in my OpenAPI spec.
- Generate a TypeScript SDK and prepare a changelog for the API change.
How to install api-docs-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install documentation-tools@wasp-nest2Manually: put the files in place
.claude/agents/api-docs-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/api-docs-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/api-docs-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about api-docs-wasp-drone
How do I install api-docs-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install documentation-tools@wasp-nest, and add .claude/agents/api-docs-wasp-drone.md.
What does api-docs-wasp-drone do?
It helps select an API reference renderer, enrich an OpenAPI spec with examples, configure publication, and prepare SDK generation. It also guides changelog entries for API changes.
What should I provide before running api-docs-wasp-drone?
Provide an OpenAPI spec as a file, URL, or API description. Validation errors stop the rendering workflow before renderer setup.