Generate a specification file from user input/requirements. Use when user says "generate spec", "create spec", "write spec", "spec from requirements", or provides feature requirements and asks to create a spec. (user)
Provides comprehensive development rules and guidelines for Cursor project development. Use when working on Cursor projects, setting up development environments, or implementing coding standards.
Apply rigorous technical writing standards when creating architecture documentation, system descriptions, component descriptions, API documentation, or any technical specification text. Use when writing descriptions for systems, actors, externals, modules, components, relationships, or interfaces.
Co-author and QA documentation such as READMEs, guides, and runbooks. Use when writing or auditing docs (not PRDs/specs).
Write meaningful code comments that explain WHY rather than WHAT, focusing on business logic, non-obvious solutions, workarounds, and complex algorithms while keeping code self-documenting. Use this skill when adding comments to explain rationale, documenting complex business logic, explaining workarounds or temporary solutions, describing performance optimizations, writing function documentation (JSDoc, docstrings, XML docs), or reviewing code for appropriate commenting. Apply when working on any code file that contains logic requiring explanation, public API functions, complex algorithms, security-critical code, or architectural decisions. This skill ensures comments explain rationale not implementation (WHY not WHAT), self-documenting code through clear naming (refactor unclear code instead of commenting), concise and evergreen comments (no who/when dated comments - Git tracks this), links to external resources for context, proper function documentation format (JSDoc for TS/JS, docstrings for Python, XML d
技術ドキュメント、機能仕様書、ビジネスコミュニケーション資料を作成します。セットアップガイド、ユーザーマニュアル、要件定義書、ステークホルダー向けレポート、インシデント報告など、あらゆるドキュメント作成をカバーします。
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
