Find the perfect capability for your agent.
Creates lightweight documentation for chore tasks and maintenance work. Use when the user needs to document a chore, maintenance task, dependency update, refactoring, or minor fix that doesn't require full feature requirements.
Writes and maintains project documentation in markdown
Create and maintain architecture documentation with Mermaid diagrams. Use when writing technical documentation, system diagrams, or updating the implementation plan.
Create and maintain architecture documentation with Mermaid diagrams. Use when writing technical documentation, system diagrams, or updating the implementation plan.
Systematically improve documentation quality from 7/10 → 9/10 using assessment checklists and transformation patterns. Use when documentation exists but lacks Quick Start, clear prerequisites, or working examples. Optimized for crypto/trading data projects.
Analyze and explain Python code in detail. Provides comprehensive explanations of functions, classes, logic, and best practices. Use when user needs detailed explanations of Python code, documentation of existing codebases, or understanding of complex programming concepts and implementations.
OpenAI Codex CLIを使用してコードレビューを実行する。Claude CodeからCodexにレビューを依頼したい時に使用。トリガー：「Codexにレビュー」「codexでコードレビュー」「差分をCodexでチェック」「Codexにコードを見てもらう」「レビューをCodexに依頼」
Write self-documenting code with minimal, helpful comments that explain logic rather than changes. Use this skill when adding comments to TypeScript files, writing JSDoc documentation, deciding whether code needs commenting, or reviewing existing comments. Apply when writing n8n node code, helper functions, or any code where you need to balance clarity with comment density.
godoc conventions and documentation best practices. Use when documenting code.
Write minimal, helpful code comments that explain why rather than what, prioritizing self-documenting code with clear structure and naming. Use this skill when adding comments to code, documenting complex logic, explaining non-obvious decisions or algorithms, writing function or class documentation, creating inline explanations for large sections of code, removing outdated or unhelpful comments, refactoring code to be more self-explanatory, or ensuring comments remain evergreen and relevant long-term. Use across all programming languages when deciding whether and how to comment code, including when writing or reviewing .js, .ts, .py, .java, .go, .rs, .rb, .php, .jsx, .tsx, .vue files or any other code files.
Load when working on documentation systems, README files, API docs, or implementing documentation workflows. Contains best practices for treating documentation as code with version control, automation, and CI/CD integration.
Provides guidance and best practices for writing simple, understandable code that developers can easily maintain
Use this skill when working on Skyline tutorials or tutorial tests.
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
TSDoc documentation standards for TypeScript following tsdoc.org conventions. WHEN: Writing TSDoc comments, documenting TypeScript functions/classes/interfaces/types, generating docs with TypeDoc, improving existing TS documentation. WHEN NOT: JavaScript code (use js-docstring), Python (use python-docstring), PHP (use php-docstring), runtime logic without documentation needs.
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
Maintain documentation freshness and code-doc alignment. Use when detecting stale documentation, suggesting doc updates during implementation, validating doc accuracy, or generating missing documentation. Handles staleness detection, coverage analysis, and doc/code synchronization.
Write self-documenting code with minimal, helpful comments that explain large sections of logic without cluttering the codebase. Use this skill when writing code comments, documenting complex logic, reviewing whether comments are needed, writing function documentation, explaining non-obvious code sections, ensuring code clarity through naming and structure, avoiding temporary or change-related comments, keeping comments evergreen and future-relevant, or deciding between adding comments versus refactoring for clarity. Apply this skill when writing or reviewing any code file to ensure comments add value without creating noise, and that code is primarily self-explanatory through clear naming and structure.
