documentation▌

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

Turn the current conversation context into a PRD and submit it as a GitHub issue.

Create clear, comprehensive code documentation using language-specific standards like JSDoc, Python docstrings, JavaDoc, and inline comments.

Expert code explanation through narratives, diagrams, and step-by-step breakdowns for all skill levels. \n \n Transforms complex algorithms, system architectures, and design patterns into clear, progressive explanations with visual aids \n Ideal for onboarding walkthroughs, learning materials, and debugging reasoning across codebases \n Delivers high-level flow summaries followed by detailed component breakdowns, pseudocode, and annotated snippets \n Highlights pitfalls, edge cases, and key term

Comprehensive toolkit for preparing ISO 13485 certification documentation for medical device Quality Management Systems.

Grounds every implementation decision in official documentation for authoritative, source-cited code.

Fetch current library documentation and code examples instead of relying on training data. \n \n Resolves library names to Context7 documentation IDs, then queries for setup, configuration, and API reference information \n Supports major frameworks and libraries: React, Vue, Svelte, Next.js, Express, Prisma, Supabase, Tailwind, and others \n Activates automatically for setup questions, code generation requests, and framework-specific inquiries \n Returns version-aware documentation and official

Organize technical documentation into four distinct types—tutorials, how-to guides, reference, and explanations—each serving different user needs. \n \n Applies the Diátaxis framework to structure documentation by learning context: tutorials for beginners learning by doing, how-to guides for solving specific problems, reference for technical facts, and explanations for conceptual understanding \n Provides type-specific patterns including title conventions, structural templates, and validation ch

Use only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities.

>-