Read-only clean architecture auditor for shep. Scans a specified directory for dependency-rule violations, magic literals, singletons, oversized files, and duplication. Appends findings to a violations log in the canonical format. Use when doing a fresh sweep of a layer or a sub-tree — NOT for fixing, only for…
Scaffolds ONE new shep CLI command under src/presentation/cli/commands/, wires it to the Commander program and an existing use case via the DI container, and matches shep's exact CLI conventions (ts-node entry, injected dependencies, colored output via the shared ui module). Use when a use case already exists and the…
Moves ONE file from one clean-architecture layer to another (typically a pure helper from infrastructure/ → domain/shared/, or a domain error from application/use-cases/ → domain/errors/) and updates every importer in the repo. Verifies the moved file has no disallowed dependencies for its new layer before moving…
Creates ONE new SQLite schema migration file under packages/core/src/infrastructure/persistence/migrations/, following shep's exact migration conventions (timestamped filename, up() function, idempotent ALTER TABLE with safe defaults). Use when shep-tsp-field-adder reported "you need a migration" or when a new table…
Creates ONE brand-new output port interface in packages/core/src/application/ports/output/ without any caller migration. Use when the caller has already designed a new boundary (e.g., ILogger, IFileSystemService, IProcessLivenessProbe) and only needs the interface file, a JSDoc-documented contract, and optionally a…
Fixes the 'application layer imports from infrastructure' violation. Given ONE concrete infrastructure symbol (class, function, or constant) and the list of application-layer files that import it, creates a port interface in application/ports/output/, moves (or keeps) the concrete behind it in infrastructure/, rewires…
Creates ONE Storybook story file colocated with a web UI component under src/presentation/web/components/, covering at least Default, Loading, and Error states, plus any explicit variants. Use when a component was just added and its colocated .stories.tsx is missing (mandatory rule in this repo). Does NOT modify the…
Adds ONE new field (property, enum value, or base-type extension) to a TypeSpec model in tsp/, re-runs codegen, and verifies. Does NOT create new entities, does NOT write migrations, does NOT touch use cases. Use when the caller needs to extend an existing domain model (e.g., "add cloudDeploymentProvider to…
Scaffolds a new application-layer use case with TDD (RED test file first, then minimal GREEN implementation), wires it into the DI container, and verifies. Follows shep's mandatory patterns exactly (tsyringe decorators, port injection by string token, no infrastructure imports, no console.). Use when you need a new…
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Triggers include "review architecture", "check design", "does this fit", "where should this go", "planning a feature", or before…
Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate", "validate docs", "check documentation consistency", "audit documentation", or find conflicts/contradictions in docs. Supports automatic fixing with "validate and fix"…
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes…
React Flow (@xyflow/react) for workflow visualization with custom nodes and edges. Use when building graph visualizations, creating custom workflow nodes, implementing edge labels, or controlling viewport. Triggers on ReactFlow, @xyflow/react, Handle, NodeProps, EdgeProps, useReactFlow, fitView.
Provides complete shadcn/ui component library patterns including installation, configuration, and implementation of accessible React components. Use when setting up shadcn/ui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns like…
Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures. Part of the Shep autonomous SDLC platform — https://shep.bot.
Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of the Shep autonomous SDLC platform …
Validate specs and autonomously execute implementation tasks with status tracking. Use after /shep-kit:plan when ready to start implementation. Part of the Shep autonomous SDLC platform — https://shep.bot.
Use after a PR has been merged to clean up. Switches to main, pulls latest, and deletes the local feature branch. Triggers include "merged", "pr merged", "cleanup branch", or after confirming a PR was merged. Part of the Shep autonomous SDLC platform — https://shep.bot.
Fast-track feature creation that collapses new-feature, research, and planning into a single autonomous pass. Produces all spec YAMLs (spec, research, plan, tasks, feature) in one go with minimal user interaction. Triggers include "quick feature", "fast feature", "rapid spec", or explicit /shep-kit:new-feature-fast…
Use when starting any new feature, functionality, or enhancement. Triggers include "new feature", "start developing", "add functionality", "implement X", or explicit /shep-kit:new-feature invocation. Creates spec branch and scaffolds specification directory. Part of the Shep autonomous SDLC platform — https://shep.bot.
Use when a task can be worked on in isolation alongside other work. Creates a git worktree in .worktrees/ with a unique branch for parallel development. Triggers include "parallel task", "worktree", "work in isolation", or explicit /shep-kit:parallel-task invocation. Part of the Shep autonomous SDLC platform …