This skill should be used when the user requests "learning mode", "teach me", "guide me through", "help me understand", "mentor me", asks for tutoring, wants to learn coding concepts through guided discovery, or prefers questions and hints over direct solutions.
Generates comprehensive Map of Content (MOC) documentation for software projects using standard markdown links, analyzing current implementation state from codebase and devlog notes
Create comprehensive spec with diagrams, flows, and thorough documentation. Use when: detailed spec, comprehensive spec, full spec, baldrick spec. Triggers on: detailed, comprehensive, full spec, thorough.
Technical documentation and knowledge management expert. Use when creating comprehensive documentation systems, improving developer knowledge sharing, or building documentation-driven development workflows.
Generate concise specifications for development tools, editors, and utilities. Use this when planning a new tool, editor plugin, or standalone utility to assist with game development.
Guidelines for creating task-oriented how-to guide documentation. Use when writing content that helps users accomplish specific goals.
Comprehensive guide for coding workflow, naming conventions, architectural principles, and API implementation patterns.
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebase familiarity
Create comprehensive technical design documents in Chinese for software projects. Use when the user requests technical architecture design, system planning, or needs a detailed technical specification document (技术方案设计.md). Focus on gathering requirements, analyzing context, and producing structured design documents with architecture diagrams, component specifications, and implementation plans.
Create structured use case documentation with sequence diagrams for backend systems. Use when documenting API endpoints, service interactions, event flows, or system behaviors. Triggers on requests like "document this use case", "create use case for X endpoint", "write flow documentation", or "explain how X feature works".
Review and analyze design docs for health, quality, and improvement opportunities. Use when auditing design documentation, checking doc health, or identifying areas for improvement.
Technical documentation specialist creating clear, comprehensive documentation including README, API docs, user guides, architecture specs, and tutorials. Use when writing project documentation, API references, setup guides, or any technical documentation requiring professional structure and clarity.
Writing clear, user-facing documentation for non-technical users. Use when creating in-app docs, help content, or feature documentation.
Guidelines for creating technical specification and API reference documentation. Use when writing factual, complete content about data models, API contracts, and configuration options.
エンドユーザー向けのマニュアル（USER_GUIDE.md）を生成・更新します。「ユーザーマニュアル更新」「マニュアル生成」「ユーザーガイド作成」などのリクエストで使用します。
This skill should be used when the user asks about "UCP architecture", "protocol structure", "OpenAPI spec", "OpenRPC spec", "capability design", "method naming", or needs to understand how UCP works. Provides guidance on UCP's layered architecture and spec generation.
Technical documentation creation with focus on clarity, UI terminology consistency, and Japanese writing quality. Use when creating or reviewing technical documentation, API docs, feature specifications, or user guides.
Creates high-quality technical documentation including API documentation, user guides, tutorials, architecture documents, README files, release notes, and technical specifications. Produces clear, structured, and comprehensive documentation following industry best practices. Use when writing technical documentation, creating API docs, developing user guides, documenting architecture, writing tutorials, preparing release notes, or when users mention "technical writing", "documentation", "API docs", "user guide", "tutorial", "README", "technical specification", "architecture document", or "developer documentation".
Guidelines for creating learning-oriented tutorial documentation. Use when writing step-by-step content that helps users learn by doing.
Expert in creating technical documentation, architectural decision records (ADRs), and RFCs. Specializes in structured knowledge management and system documentation. Use when writing technical docs, ADRs, RFCs, or system design documents.
Guidelines for creating architecture overview and system explanation documentation. Use when writing content that clarifies system design, data flow, and architectural concepts.
Creates technical design documents covering architecture, APIs, data models, and implementation approach. Bridges requirements to implementation. Use when designing system architecture, API contracts, or complex technical solutions.
This skill should be used when the user asks to 'create an article', 'add a blog post', 'modify frontmatter', 'add a category', or 'update content schema'. Provides guidance for MDX articles, content-collections, and static content data in content/articles/*.mdx, content/data/*.ts, content-collections.ts.
