technical-documentation
Write clear technical documentation, API references, user guides, tutorials, and architecture docs. Use when creating or updating documentation.
Write clear technical documentation, API references, user guides, tutorials, and architecture docs. Use when creating or updating documentation.
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
Annotation and documentation protocol for rapid-iteration projects (“vibe coding”). Enforces Google Docstring Style plus comment-as-contract: consistency with signatures/types, explicit pre/post-conditions, units/frames/conventions, and rich implementation comments. Use Notes with ASCII + pseudocode for complex algorithms.
Explain code in plain English with visual diagrams. Use when user wants to understand how code works or needs documentation.
代码变更后自动同步开发文档。支持功能文档、技术设计、决策记录的智能更新。当用户提到更新文档、同步文档、完成功能、修改数据结构或新增KPI时激活。
Write Python docstrings following PEP 257 and popular formats (Google, NumPy, Sphinx). WHEN: Writing docstrings for Python functions/classes/modules, choosing docstring format, documenting parameters/returns/exceptions. WHEN NOT: JavaScript documentation (use js-docstring), TypeScript (use ts-docstring), PHP (use php-docstring), general code comments.
Documentation-first development methodology. The goal is AI-ready documentation - when docs are clear enough, code generation becomes automatic. Triggers on "Build", "Create", "Implement", "Document", or "Spec out". Version 3.4 adds complete 13-item Clarity Gate with scoring rubric and self-assessment.
Generate detailed API contracts and specifications including OpenAPI/Swagger definitions, endpoint documentation, and integration guidelines
Remove historical cruft from design docs. Use when docs accumulate outdated content, after major refactorings, or when preparing for releases.
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
Use this skill when you are creating documentation for an existing Connect feature or updating existing docs
Unity開発の公式ドキュメント検索、最新API情報、パフォーマンス最適化、ベストプラクティスを案内するガイドエージェント。Unity Engine/Editor API、UPM/NuGetパッケージ、YAML設定ファイル編集に関する質問や実装支援で使用される。
文档生成技能:提供标准化的文档编写工作流和模板。 Use when: 需要编写组件文档、API 文档、模块 README、项目文档。 Triggers: "文档", "documentation", "README", "API 文档", "组件文档", "注释"
README, 마크다운 문서, 아키텍처 문서 등 사용자가 읽을 수 있는 문서를 작성할 때 사용. 다이어그램 형식과 문서 구조 가이드라인을 따름.
Activates when creating or improving technical documentation, READMEs, and API docs
Create a comprehensive inventory of a codebase. Map structure, entry points, services, infrastructure, domain models, and data flows. Pure documentation—no opinions or recommendations.
Convert a draft document into an executable spec.json with trackable stories
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
Generate Twoslash code examples for RSPress documentation. Use when adding type-rich, interactive code examples to documentation pages.
Generate a complete software specification document for the current project/repo, including architecture, data model, key processes, pseudocode, and Mermaid diagrams (context, container/deployment, module relations, sequence, ER, class, flowchart, state).