documentation-updater
Skill para mantener la documentación sincronizada con el código. Incluye patrones de documentación, ubicaciones estándar, y checklists.
Skill para mantener la documentación sincronizada con el código. Incluye patrones de documentación, ubicaciones estándar, y checklists.
Pythonファイルの挙動を理解するために、挙動を変えずに解説コメントとdocstringを追加する。ユーザーが「XXX.pyについて、動作を理解したいから細かくコメント入れて」「挙動は変えずにコメントを足して」「このPythonファイルに解説を入れて」などと言ったときに使う。
JSDoc documentation standards for JavaScript following jsdoc.app conventions. WHEN: Writing JSDoc comments, documenting JavaScript functions/classes/modules, generating API docs with JSDoc, improving existing JS documentation. WHEN NOT: TypeScript code (use ts-docstring), Python (use python-docstring), PHP (use php-docstring), runtime logic without documentation needs.
Standardized procedure to generate developer API documentation for C++ libraries and Python modules.
Write detailed product and technical specification documents for OrbitCove. Use when creating PRDs, architecture docs, data models, or UX flows.
Keep the structure of documentation clear and explicit.
Updates documentation after code changes to keep docs in sync with code reality. Use AFTER implementation is complete. Covers feature docs, workflow docs, and index files.
Generate Japanese documentation from spec files. Use AUTOMATICALLY after writing or editing any file matching specs/**/*.md (excluding specs/**/docs/*). Also use when user says "generate spec docs", "spec docs", "PM docs", "architect docs", or "implementation guide". (user)
Busca documentación oficial de APIs/libraries (version-specific). Usa Context7 o WebFetch para docs reales, no inventa.
プロジェクトの開発ガイドライン(docs/development-guidelines.md)を新規作成/更新する。「コーディング規約を作って」「開発ルールを整理」「コード規約」「レビューガイドライン」「テスト方針を決めて」などの依頼時に使用。コーディング規約と開発プロセスの2本立てで、具体例と理由、測定可能な基準を含める。
Demonstrates progressive disclosure by loading reference documentation on demand. Shows how skills can include additional detailed documentation without loading everything upfront.
Guide for writing Rust code covering ownership, borrowing, lifetimes, error handling, async programming, and Rust best practices
Complete skill guide for AI agents to write proper Odoo 18 code. This master file references detailed guides for each topic including models, fields, decorators, views, performance optimization, controllers, and development best practices. Use this skill when writing, reviewing, or refactoring Odoo 18 code to ensure proper ORM patterns, API usage, and performance optimization.
General documentation standards for README, AsciiDoc, and technical documentation
Write prosaic, narrative-style documentation for Lean 4 libraries. Use when creating README files, user guides, tutorials, or comprehensive library documentation.
Generate a library-specific documentation/source reference skill
Fetches up-to-date, version-aware library documentation from the Context7 MCP server before working on a project.
Documentation standards. Apply when completing full feature development, introducing new architecture patterns, or adding new public APIs.
Comprehensive Ruby on Rails v8.1 development guide with detailed documentation for Active Record, controllers, views, routing, testing, jobs, mailers, and more. Use when working on Rails applications, building Rails features, debugging Rails code, writing migrations, setting up associations, configuring Rails apps, or answering questions about Rails best practices and patterns.
Add Google-style docstrings to modules. Use for documentation requests.
Generate MkDocs documentation sites with Material theme, mkdocstrings for API docs, and versioning. Use when setting up or extending project documentation.