ๅบไบ Markdown ็ฌ่ฎฐ๏ผไป ็จๅ จ้จๆ ้ขไธๅฐ้ๆญฃๆ็บฟ็ดข๏ผ็ๆๅญฆไน ็ฌ่ฎฐ้ๆๆธ ๅ๏ผๆฐ่งๅ็ฎๅฝ๏ผๅบ็กโ่ฟ้ถ๏ผใๆงๆ ้ขโๆฐ็ฎๅฝๆ ๅฐใ้ๅฝๅๅปบ่ฎฎ๏ผ้ตๅพช planning-with-files๏ผtask_plan/notes๏ผไธ learning-notes-organizer ็้ๅ่พน็/ๅฝ็ฑป้็ปๆ่ทฏ๏ผไธๆนๆญฃๆใ
่ฎฐๅฟๅบ - ่ทจไผ่ฏ็ฅ่ฏๆไน ๅ็ฎก็ใไฝไธบ้กน็ฎไธไธๆ็ๅฏไธ็ๅฎๆฅๆบใ
Check the current status of Codex collaboration. Use when user says codex status, check codex, or collaboration status.
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
Use for WRITING documentation with ready-to-use code templates (C# XML docs, TypeScript JSDoc, API docs, README patterns). Best for implementing actual documentation, adding code comments, and creating docs from scratch. NOT for documentation planning (use documentation instead).
Use when designing or architecting Rust applications, creating comprehensive project documentation, planning async/await patterns, defining domain models with ownership strategies, structuring multi-crate workspaces, or preparing handoff documentation for Director/Implementor AI collaboration
ใใญใฅใกใณใใจใณใผใใฎไน้ขใ็ฃๆปใAPIใจใณใใใคใณใใในใญใผใใ่จญๅฎใใกใคใซใจใใญใฅใกใณใใๆฏ่ผใใไธๆดๅใใฌใใผใใๅฎๆ็ใชใใญใฅใกใณใใใซในใใงใใฏใซไฝฟ็จใ
Efficiently navigate codebase documentation during Research phase. Use instead of Grep/Glob for finding architectural decisions, feature specs, and technical docs. Maps topics to doc locations for fast context retrieval. If codebase lacks documentation structure, provides patterns to establish one.
Guide for creating Claude Code skill documents with YAML frontmatter, instructions, examples, and reference implementations
API ๆๆกฃ็ๆๅทฅๅ ทใ้็จไบไปปไฝๅ็ซฏๆๆฏๆ ็ API ๆฅๅฃๆๆกฃ็ๆๅ็ปดๆค๏ผ็กฎไฟๅๅ็ซฏๆฅๅฃ่ง่็ปไธใ
Use for WRITING documentation with ready-to-use code templates (C# XML docs, TypeScript JSDoc, API docs, README patterns). Best for implementing actual documentation, adding code comments, and creating docs from scratch. NOT for documentation planning (use documentation instead).
Manage implementation logs in _docs/templates/ with consistent format. Use when starting project work, completing implementations, or when user mentions ๅฎ่ฃ ใญใฐ/implementation log.
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
Use when writing documentation, READMEs, explanations, blog posts, or any prose meant for humans to read
Use when creating or updating technical documentation, API documentation, or inline code documentation.
Refreshes README.md documentation tables including the packages table and core namespace index. Reads from package.json files and core module JSDoc.
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
Generate enterprise module documentation with 26-section structure and folder hierarchy. Use for module docs, enterprise features, detailed specs in docs/business-features/{Module}/. Includes README, INDEX, API-REFERENCE, detailed-features/. Triggers on "module docs", "enterprise feature docs", "business module", "26-section docs", "detailed feature specs". For single-file quick docs, use feature-docs instead.
Complete getting started guide for Universe 2025 (Tufty) Badge from zero to first app. Use when helping absolute beginners, providing step-by-step first-time setup, or when users ask "how do I get started", "where do I begin", or "first steps with the badge".
Alice's couch-to-5K retrospective with training reflections and progress tracking.
