Loading...
Loading...
Found 45 Skills
Capture technical breakthroughs and transform them into actionable, reusable documentation. Use this skill when the user has achieved a significant technical insight, solved a hard problem, discovered a non-obvious solution, or wants to document a breakthrough moment. Also trigger when the user mentions "eureka", "breakthrough", "document this insight", "capture this discovery", or wants to turn a technical win into reusable knowledge.
Skill for researching best practices. Triggered when you need to understand methodologies, tools, and best practices in a specific field. Trigger words: research, learn about, what methods are there, best practices.
Conducts in-depth analysis of a specific source or topic, producing comprehensive summaries for research synthesis. Use when you need detailed analysis and documentation of individual sources as part of a larger research effort.
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
Narrative templates for git history documentation. Used by /git:code-story command.
Write unambiguous specifications using EARS (Easy Approach to Requirements Syntax) patterns. Provides 6 sentence templates that eliminate ambiguity: Ubiquitous, Event-driven, State-driven, Unwanted behavior, Optional feature, and Complex. Use when: "EARS", "specification writing", "write specs", "仕様を書く", "EARS記法", "仕様を明確化", "requirements specification", "unambiguous specification".
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.
Run the Phase 0 research workflow to scaffold research artifacts before task planning.