Skill Claude Code
Use this whenever the user asks to "create a module", "scaffold a feature", "add a Vue domain", "new module called X", or starts work on a brand-new vertical (views + components + store + router entry + tests). Duplicates the canonical src/modules/tasks template, applies kebab/Pascal/camel/ UPPER renames, and wires…
Skill Claude Code
Use this whenever the user asks to "implement", "add", "build", "create", or "modify" a feature, page, view, component, or module in this Vue project. Three phases: Phase 0 scope analysis (flows + edge cases + UI needs + plan validation, STOP for user), Phase 1 implementation (layered UI → Store → API, Vue 3…
Skill Claude Code
Use this whenever a new file/folder is created or renamed in this Vue project, when reviewing a module for consistency, or when the right path for a file is unclear. Also triggers on "what should I name this?", "is this file named correctly?", "audit module naming". Enforces kebab-case folders, dot-prefixed…
Skill Claude Code
Use this whenever the user asks to "open a PR", "ship this", "create the pull request", "make a PR", or once a Vue feature/fix is verified and ready to push. Full lifecycle: branch → commit (commitizen) → issue → draft PR → CI → ready → autonomous monitor loop (fix comments, resolve threads, iterate until CI green +…
Skill Claude Code
Design system reference for the Devkit Vue stack (Vuetify 4 + custom theme helpers). Use when asked about styling, theming, layout, design system, Vuetify components, visual verification, or UI patterns. Automatically consumed by /feature when the task has a visual component. Can also be invoked directly for…
Skill Claude Code
Use this whenever a downstream Vue project needs to absorb upstream Devkit Vue changes — triggers on "update stack", "sync with devkit", "merge upstream", "pull stack updates", "resolve stack conflicts". Two-phase: ISO merge (stack modules stay byte-identical to upstream) then project alignment (apply MIGRATIONS.md…
Skill Claude Code
Run this after every code change in this Vue project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "build", "audit". Diff audit (router guards, store boundaries, UX, /ui consistency, error handling) → lint → tests + coverage gate → build. Coverage drops →…
Skill Claude Code
Use this whenever the user asks to "create a module", "scaffold a feature", "add a domain", "new module called X", or starts work on a brand-new vertical (controller + service + repo + model + routes + tests). Duplicates the canonical modules/tasks template, applies kebab/Pascal/camel renames, and registers…
Skill Claude Code
Use this whenever the user asks to "implement", "add", "build", "create", or "modify" a feature, endpoint, API, route, or module in this Node project. Three phases: Phase 0 scope analysis (flows + edge cases + plan validation, STOP for user), Phase 1 implementation (layered Routes → Controllers → Services →…
Skill Claude Code
Use this whenever a new file/folder is created or renamed in this Node project, when reviewing a module for consistency, or when the right path for a file is unclear. Also triggers on "what should I name this?", "is this file named correctly?", "audit module naming". Enforces kebab-case folders…
Skill Claude Code
Use this whenever the user asks to "open a PR", "ship this", "create the pull request", "make a PR", or once a feature/fix is verified and ready to push. Full lifecycle: branch → commit (commitizen) → issue → draft PR → CI → ready → autonomous monitor loop (fix comments, resolve threads, iterate until CI green + zero…
Skill Claude Code
Use this whenever a downstream Node project needs to absorb upstream Devkit Node changes — triggers on "update stack", "sync with devkit", "merge upstream", "pull stack updates", "resolve stack conflicts". Two-phase: ISO merge (stack modules + lib stay byte-identical to upstream) then project alignment (apply…
Skill Claude Code
Run this after every code change in this Node project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "audit". Diff audit (architecture, security, naming, error handling) → lint → tests + coverage gate. Coverage drops → add tests, never lower thresholds.…
Command GitHub Copilot
Full playbook: .claude/skills/create-module/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/feature/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/naming/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/pull-request/SKILL.md Monitoring commands: .claude/skills/pull-request/references/monitoring.md.
Command GitHub Copilot
Full playbook: .claude/skills/update-stack/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/verify/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/create-module/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/feature/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/naming/SKILL.md.
Command GitHub Copilot
Full playbook: .claude/skills/pull-request/SKILL.md Monitoring commands: .claude/skills/pull-request/references/monitoring.md.
Command GitHub Copilot
Full playbook: .claude/skills/update-stack/SKILL.md.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: