audit-stackScan a project''s source code and produce a stack audit with technology layers, architecture recommendations, and template/stack.json generation suggestions Arguments: Path to project directory (defaults to current directory).
audit-stackUse when the user asks to "audit project stack", "analyze technologies", "scan dependencies", "generate stack.json", "what template level is this project", "map project to layers", or wants to discover all technologies in a codebase and get template and stack.json recommendations.
captureQuick-capture an improvement idea without interrupting work — saves to backlog for later processing during wrap-up Arguments: Quick note (e.g., ''directus-dev missing cache gotcha'', ''add VERCEL_TOKEN to L1 .env.example'').
captureUse this skill when the user says "capture this", "note this for later", "remember to fix this", "save this improvement", "add to backlog", "I'll fix this later", or wants to quickly jot down an improvement idea without interrupting their current work. Defers routing and application to the wrap-up s
createCreate a new project template at Level 1, 1.5, or 2 by cloning and customizing a parent template Arguments: Template description (e.g., ''Level 1 template for Directus + Next.js'', ''demo for Supabase + Nuxt'').
createUse this skill when the user asks to "create a new template", "scaffold a Level 1 template", "create project-{stack}", "make a new stack template", "fork project-template", "create a demo template", "set up a new project from template", or wants to create any new project template at Level 1, 1.5, or
feedbackReport an issue in the current project that should be fixed in a parent template (Level 0 or Level 1) Arguments: Description of what to fix (e.g., ''add VERCEL_TOKEN to .env.example'', ''create a new-api-route skill'').
feedbackUse this skill when the user says "this should be in the parent template", "fix the template", "add this to project-template", "send feedback to parent", "improve the base template", "this skill belongs in the template", "update the parent", "push this up to the template", "the template needs this",
improveUnified improvement — auto-routes fixes to the correct plugin or parent template based on what kind of knowledge it is Arguments: Description of what to improve (e.g., ''directus-dev sdk-patterns needs cache gotcha'', ''add VERCEL_TOKEN to .env.example'').
improveUse this skill when the user says "improve", "this should be better", "fix this in the source", "this belongs in the plugin", "this belongs in the template", "push this upstream", "improve the plugin", "improve the template", or discovers any improvement while working in a child project that should
syncSync the current child project from its parent template — pull latest skills, commands, rules, and configs
syncUse this skill when the user says "sync from parent", "pull template changes", "merge parent template", "update from project-template", "my project is out of sync", "get latest template changes", "sync template", or needs to propagate improvements from a parent template (Level 0 or Level 1) down to
template-referenceUse this skill when the user asks about "template hierarchy", "template levels", "project template conventions", "what files go in a template", "Level 0 vs Level 1", "template structure", "what belongs in the parent template", or needs reference documentation for the project template system and its
validateValidate a project template against Level 0/1/1.5/2 conventions and required file structure Arguments: Path to template directory (defaults to current directory).
validateUse this skill when the user asks to "validate template", "check template structure", "is my template correct", "verify template conventions", "validate project template", "check template files", or needs to verify that a project template follows the Level 0/1/1.5/2 conventions and has all required
wrap-upEnd-of-session review — find plugin and template improvements, process captured backlog, push fixes to sources
wrap-upUse this skill when the user says "wrap up", "end session", "done for today", "session review", "what should go into the template", "template improvements", "save template learnings", "review what we did for the template", "plugin improvements", "what should go into the plugin", or at the end of a w