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).