documentation-audit
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
Use when writing documentation, READMEs, explanations, blog posts, or any prose meant for humans to read
Use when creating or updating technical documentation, API documentation, or inline code documentation.
Refreshes README.md documentation tables including the packages table and core namespace index. Reads from package.json files and core module JSDoc.
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
Generate enterprise module documentation with 26-section structure and folder hierarchy. Use for module docs, enterprise features, detailed specs in docs/business-features/{Module}/. Includes README, INDEX, API-REFERENCE, detailed-features/. Triggers on "module docs", "enterprise feature docs", "business module", "26-section docs", "detailed feature specs". For single-file quick docs, use feature-docs instead.
Technical specification writing for implementation details. Use when documenting how to build a solution (post-decision), API contracts, schemas, and system design. Complements RFC skill which handles decision-making.
Generate standardized document templates (DOCUMENT, TECHNICAL, PROPOSAL, RESEARCH, SECURITY-QA, INDEX) with YAML frontmatter, Quick Reference sections, and consistent structure for professional documentation.
Updates documentation (READMEs and store descriptions) across multiple languages.
Transform markdown knowledge repositories into Claude skills. Analyzes knowledge bases, generates SKILL.md files with appropriate loading strategies, and packages distributable skills. Use when creating skills from documentation, frameworks, or knowledge gardens.
OpenAPI仕様の専門スキル。 API定義、スキーマ設計、ドキュメント生成を提供します。 Anchors: • 『OpenAPI Specification』(Linux Foundation) / 適用: API仕様設計 / 目的: REST API標準化 • 『RESTful API設計のベストプラクティス』(複数出典) / 適用: エンドポイント設計 / 目的: 一貫性確保 Trigger: OpenAPI仕様書作成時、API定義ドキュメント作成時、Swagger仕様設計時に使用
Build modern documentation websites with Docusaurus. Covers docs, blog, pages, versioning, i18n, search integration, and deployment patterns. React-based with MDX support for interactive documentation.
Creates or updates documentation in a type-agnostic manner by dynamically loading type-specific context at runtime
Comprehensive error documentation patterns for APIs, libraries, and systems. Covers error catalogs, troubleshooting guides, recovery procedures, and runbook creation to improve developer experience and reduce support burden. Anchors: • The Pragmatic Programmer (Hunt, Thomas) / 適用: error communication / 目的: clear actionable messages • Site Reliability Engineering (Google) / 適用: runbook patterns / 目的: operational excellence • API Design Patterns (JJ Geewax) / 適用: error response design / 目的: consistent error contracts Trigger: Use when documenting API errors, creating error catalogs, writing troubleshooting guides, designing runbooks, standardizing error responses, improving error discoverability.
Generate code comments and docstrings. Use when user asks to "add comments", "document this code", "explain with comments", or "add docstrings".
Use when writing or enhancing Swift documentation comments for DocC generation, adding inline doc comments to Swift source files, or when user asks for API documentation
How to create & maintain TypeDoc site documentation and the README for Bupkis
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
IEEE 830やDoc as Codeなどの標準に基づき、技術文書の構造と品質基準を整えるスキル。 テンプレート適用と検証フローを通じて、再利用性と明確性を高める。 Anchors: • IEEE 830 / 適用: 仕様書構造 / 目的: 標準化 • Documentation as Code / 適用: 文書運用 / 目的: 継続的管理 • Software Requirements (Karl Wiegers) / 適用: 要求記述 / 目的: 明確性 Trigger: Use when defining documentation standards, creating SRS templates, or reviewing technical docs for consistency. documentation standards, IEEE 830, SRS, doc-as-code, documentation review
Enforces online documentation research before any technical implementation. Use when implementing features to ensure code follows current best practices by researching official documentation first.
Expert Django backend development guidance. Use when creating Django models, views, serializers, or APIs; debugging ORM queries or migrations; optimizing database performance; implementing authentication; writing tests; or working with Django REST Framework. Follows Django best practices and modern patterns.
Use when setting up DocC documentation for a Swift package, deploying to GitHub Pages, or encountering "no such module 'UIKit'" during doc generation
OpenAPI、Swagger、RESTful APIドキュメンテーションのベストプラクティスを提供する専門スキル。 Anchors: • 『RESTful Web APIs』(Leonard Richardson)/ 適用: REST APIドキュメンテーション / 目的: リソース設計とHTTP操作の標準化 Trigger: OpenAPI/Swagger定義設計時、APIエンドポイント仕様書作成時、REST APIドキュメント整備時、認証仕様文書化時、エラーレスポンス標準化時、ドキュメントレビュー時に使用