- **Spec-Driven:** Code must exist in `@specs/` before it exists in `src/`.
Sign in to like and favorite skills
@specs/src/@docs/@memory/Match the user request to the Trigger and invoke the Skill.
| Skill Name | One-Liner Description | Trigger Keywords / Intent |
|---|---|---|
| Scaffolds the SDD folder structure. | "Init", "Setup", "Start new", "Onboard existing" |
| Maps codebase without reading full files. | "Explore", "Map code", "Where is X", "Understand structure" |
| Researches stacks & writes Specs. | "Design", "Research stack", "Choose DB", "Architecture" |
| Deep research & spec writing for new feats. | "Add feature", "Create page", "New capability", "How to implement" |
| Breaks specs into atomic tasks. | "Plan", "Break down", "Create tasks", "What next?" |
| Finds & scrapes official documentation. | "Find docs", "Get manual", "Update docs", "How do I use lib X?" |
| Writes & verifies code (One task at a time). | "Build", "Implement", "Code this", "Do task 1" |
| Adversarial code review. | "Review", "Check my work", "Audit", "Find bugs" |
| Modifies existing specs/logic. | "Change requirement", "Update logic", "Refactor", "Pivot" |
| Manages long-term project history. | "Save context", "Wrap up", "Restore session", "What did we do?" |
| Debugging & Deployment config. | "Debug", "Fix crash", "Deploy", "Docker", "CI/CD" |