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 documenting APIs, packages, or public interfaces.
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.
Formats and writes session documentation to the appropriate location. Use when creating session logs or documentation entries.
godoc conventions and documentation best practices. Use when documenting code.
How to create Claude Code skill documents with YAML frontmatter, instructions, examples, and reference material
Generate a local development environment plan for any stack. Use when user asks for local dev setup instructions, docker-compose configuration, or how to run a stack locally.
Generate API documentation from TypeScript source code for RSPress. Use when documenting package APIs, extracting types from source code, or creating function/class reference pages.
チーム全体で統一された開発プロセスとコーディング規約を確立するための包括的なガイドとテンプレート。開発ガイドライン作成時、コード実装時に使用する。
Guides implementation phase. Use when writing code, implementing features, or building functionality. Ensures code quality, testing, and documentation.
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.
Guidelines for writing effective Clojure docstrings with markdown formatting, wikilinks, code examples, and tables. Always use this skill when writing or reviewing docstrings in Clojure code, or when asked about docstring formatting and style. Triggers on (1) writing new functions/vars/namespaces with docstrings, (2) updating existing docstrings, (3) questions about docstring best practices, (4) reviewing code with docstrings.
コード変更、API変更、新機能追加時にドキュメントを自動更新します。公開APIやインターフェースの変更、新クラス・関数・モジュールの追加、アーキテクチャの重要な変更、ユーザーからの明示的なドキュメント更新依頼時に起動します。プロジェクトのドキュメント標準に準拠した更新を提案します。
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.
Provide repository-wide documentation guidelines under `docs/`. Use tool-based inspection first, and keep `README.md` and `docs/` in sync with the current state of the app.
This skill should be used when users need to create, validate, or modify Moqui framework services, entities, and queries. It provides comprehensive guidance for writing correct Moqui XML definitions, following framework patterns and conventions.
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
