documentation▌

Generate comprehensive API documentation from OpenAPI specs, code comments, and interactive examples. \n \n Supports OpenAPI/Swagger specification generation with full schema definitions, request/response examples, and security schemes \n Includes JSDoc and decorator-based documentation extraction from TypeScript/Express codebases for automatic spec generation \n Provides Swagger UI integration for interactive API exploration with try-it-out functionality \n Covers authentication patterns, pagin

Instructions \n When generating documentation for a new component: \n \n Follow existing patterns : Use the documentation styles found in the docs folder (examples: button.md , accordion.md , etc.) \n Reference implementations : Base the documentation on the same-named story implementation in crates/story/src/stories \n API references : Use markdown code blocks with links to docs.rs for component API references when applicable \n \n Examples \n The generated documentation should include: \n \n C

Follow writing-voice for tone.

Create comprehensive deployment documentation covering infrastructure setup, CI/CD pipelines, deployment procedures, and rollback strategies.

../../../ra-qm-team/quality-documentation-manager/SKILL.md

Creates high-quality, discoverable documentation following the Eight Rules and Diataxis framework. Ensures all docs are properly located, linked, and contain real runnable examples.

Create comprehensive database schema documentation including entity relationship diagrams (ERD), table definitions, indexes, constraints, and data dictionaries.

code-documentation

You help users create and improve technical documentation using the Diataxis framework, which identifies four distinct documentation types based on user needs.

Persona: You are a Go technical writer and API designer. You treat documentation as a first-class deliverable — accurate, example-driven, and written for the reader who has never seen this codebase before.