Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Guides technical documentation and report writing. Applies the 7 Cs principle (Clear, Concise, Correct, Coherent, Concrete, Complete, Courteous). Use for writing technical documents, reports, and code comments.
Guides Go development with best practices from Google Style Guide and Effective Go. Use when go.mod is detected or Go code is being written. Covers naming, error handling, concurrency, testing, and project stru...
Esta skill debe usarse cuando el usuario pide "documentar un patrón", "documentar un problema", "documentar una decisión", "documentar guías", "documentar la sesión", "crear documentación de", o quiere capturar...
Documentation creation and modification rules (docs/develop/ design documents, abstraction principles, structure). Use when creating documentation, updating design documents, writing architecture docs, asking a...
Creates technical design documents covering architecture, APIs, data models, and implementation approach. Bridges requirements to implementation. Use when designing system architecture, API contracts, or comple...
Verifies API documentation against source code to eliminate fabricated claims, ensure accuracy, and validate examples. Zero tolerance for unverified claims, marketing language, or non-runnable code examples. Us...
Creates problem-oriented migration guides following Diátaxis How-To pattern. Maps old APIs to new APIs with before/after examples, documents breaking changes, provides troubleshooting. Zero tolerance for fabric...
Creates comprehensive API reference documentation following Diátaxis Reference pattern. Reads source code to verify every method signature, creates structured API docs with zero fabrication tolerance. Use when...
Creates beginner-friendly, learning-oriented tutorials following Diátaxis Tutorial pattern. Step-by-step guides with success criteria, time estimates, and complete working examples. Zero tolerance for fabricate...
Guide for updating X-Fidelity documentation including README and website. Use when updating docs, adding new features to documentation, or ensuring docs stay in sync with code.
Transform documentation from any starting point into professional, comprehensive documentation packages using the Diátaxis framework. 7 commands: init (create structure), inventory (catalog sources), plan (crea...
開発作業の要件定義書（requirements.md）を生成します。このスキルは単独で使用することも、generate-working-docsから呼び出されることもあります。
開発作業ドキュメントを自動生成します。YYYYMMDD_要件名の形式でディレクトリを作成し、requirements.md、design.md、tasklist.md、testing.mdを生成します。「開発作業ドキュメント作成」「新規開発のドキュメント作って」「...
開発作業のテスト手順書（testing.md）を生成します。このスキルは単独で使用することも、generate-working-docsから呼び出されることもあります。
開発作業の設計書（design.md）を生成します。このスキルは単独で使用することも、generate-working-docsから呼び出されることもあります。
Use when asked to introduce Codex SDK usage for automation (CI/CD, bots, internal tools) and provide a minimal, safe starter pattern.
技術設計書を作成・編集します。アーキテクチャ設計、コンポーネント定義、API設計、データベーススキーマの文書化が必要な場合に使用してください。requirements/が存在する場合は整合性を確認します。
Provides general code quality and best practices guidance applicable across languages and frameworks. Focuses on linting, testing, and type safety.
Create clear feature documentation for non-professional developers. Use PROACTIVELY when documenting new features, significant code changes, creating technical specifications, or when a feature isn't covered in...
Technical documentation creation with focus on clarity, UI terminology consistency, and Japanese writing quality. Use when creating or reviewing technical documentation, API docs, feature specifications, or use...
Systematic documentation review following document-writer principles. Use when user requests documentation review, quality check, or principle compliance verification.
Outline extension implementing protocol for documentation domain
General documentation standards for README, AsciiDoc, and technical documentation with validation, formatting, link verification, and content review workflows
JavaDoc documentation standards including class, method, and code example patterns
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.