Write trustworthy developer reference: drive it from the spec (OpenAPI/AsyncAPI) so it can't drift, make every example runnable, document the unhappy path (errors/limits/auth/pagination), and optimize the quickstart for time-to-first-success.
How this skill is triggered — by the user, by Claude, or both
Slash command
/technical-writing-docs:api-reference-writingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate reference from the OpenAPI/AsyncAPI (api-engineering); enrich with prose + examples. It can't drift from the contract that way.
Generate reference from the OpenAPI/AsyncAPI (api-engineering); enrich with prose + examples. It can't drift from the contract that way.
Test every snippet (or extract from tested code). A failing quickstart example is an active trust-destroyer.
Document errors (real shapes), rate limits, auth/scopes, pagination, idempotency — needed exactly when the happy path fails.
The quickstart's job: zero -> a working call in minutes. Optimize it ruthlessly. READMEs answer what/why/how/where.
npx claudepluginhub mcorbett51090/ravenclaude --plugin technical-writing-docsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.