feat(commands): make dispatch files active command handlers

All 25 dispatch files now have name: in frontmatter with Workflow
section that displays sub-commands and prompts for selection.
Bare /noun invocation is now useful instead of a dead end.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-08 19:12:12 -05:00
parent bbce9ed321
commit 271e0210a5
25 changed files with 324 additions and 89 deletions

View File

@@ -1,14 +1,23 @@
--- ---
description: Prompt optimization and requirement clarification name: clarity
description: Prompt optimization and requirement clarification — type /clarity <action> for commands
--- ---
# /clarity # /clarity
Prompt optimization and requirement clarification with ND-friendly accommodations. Prompt optimization and requirement clarification with ND-friendly accommodations.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/clarity clarify` | Full 4-D methodology for complex requests | | `/clarity clarify` | Full 4-D methodology for complex requests |
| `/clarity quick-clarify` | Rapid mode for simple disambiguation | | `/clarity quick-clarify` | Rapid mode for simple disambiguation |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,15 +1,18 @@
--- ---
description: CLAUDE.md and settings optimization name: claude-config
description: CLAUDE.md and settings optimization — type /claude-config <action> for commands
--- ---
# /claude-config # /claude-config
CLAUDE.md and settings.local.json optimization for Claude Code projects. CLAUDE.md and settings.local.json optimization for Claude Code projects.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/claude-config analyze` | Analyze CLAUDE.md for optimization opportunities | | `/claude-config analyze` | Analyze CLAUDE.md for optimization opportunities |
| `/claude-config optimize` | Optimize CLAUDE.md structure with preview/backup | | `/claude-config optimize` | Optimize CLAUDE.md structure with preview/backup |
| `/claude-config init` | Initialize new CLAUDE.md for a project | | `/claude-config init` | Initialize new CLAUDE.md for a project |
@@ -18,3 +21,9 @@ CLAUDE.md and settings.local.json optimization for Claude Code projects.
| `/claude-config audit-settings` | Audit settings.local.json permissions (100-point score) | | `/claude-config audit-settings` | Audit settings.local.json permissions (100-point score) |
| `/claude-config optimize-settings` | Optimize permissions (profiles, consolidation, dry-run) | | `/claude-config optimize-settings` | Optimize permissions (profiles, consolidation, dry-run) |
| `/claude-config permissions-map` | Visual review layer + permission coverage map | | `/claude-config permissions-map` | Visual review layer + permission coverage map |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,14 +1,16 @@
--- ---
description: NetBox CMDB infrastructure management name: cmdb
description: NetBox CMDB infrastructure management — type /cmdb <action> for commands
--- ---
# /cmdb # /cmdb
NetBox CMDB integration for infrastructure management. NetBox CMDB integration for infrastructure management.
When invoked without a sub-command, display available actions and ask which to run.
## Sub-commands ## Available Commands
| Sub-command | Description | | Command | Description |
|-------------|-------------| |-------------|-------------|
| `/cmdb search` | Search NetBox for devices, IPs, sites | | `/cmdb search` | Search NetBox for devices, IPs, sites |
| `/cmdb device` | Manage network devices (create, view, update, delete) | | `/cmdb device` | Manage network devices (create, view, update, delete) |
@@ -21,3 +23,9 @@ NetBox CMDB integration for infrastructure management.
| `/cmdb change-audit` | NetBox audit trail queries with filtering | | `/cmdb change-audit` | NetBox audit trail queries with filtering |
| `/cmdb ip-conflicts` | Detect IP conflicts and overlapping prefixes | | `/cmdb ip-conflicts` | Detect IP conflicts and overlapping prefixes |
| `/cmdb setup` | Setup wizard for NetBox MCP server | | `/cmdb setup` | Setup wizard for NetBox MCP server |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,15 +1,24 @@
--- ---
description: Security scanning and code refactoring name: sentinel
description: Security scanning and code refactoring — type /sentinel <action> for commands
--- ---
# /sentinel # /sentinel
Security scanning and safe code refactoring tools. Security scanning and safe code refactoring tools.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/sentinel scan` | Full security audit (SQL injection, XSS, secrets, etc.) | | `/sentinel scan` | Full security audit (SQL injection, XSS, secrets, etc.) |
| `/sentinel refactor` | Apply refactoring patterns to improve code | | `/sentinel refactor` | Apply refactoring patterns to improve code |
| `/sentinel refactor-dry` | Preview refactoring without applying changes | | `/sentinel refactor-dry` | Preview refactoring without applying changes |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,14 +1,16 @@
--- ---
description: Cross-plugin compatibility validation name: cv
description: Cross-plugin compatibility validation — type /cv <action> for commands
--- ---
# /cv # /cv
Cross-plugin compatibility validation and agent verification. Cross-plugin compatibility validation and agent verification.
When invoked without a sub-command, display available actions and ask which to run.
## Sub-commands ## Available Commands
| Sub-command | Description | | Command | Description |
|-------------|-------------| |-------------|-------------|
| `/cv validate` | Full marketplace compatibility validation | | `/cv validate` | Full marketplace compatibility validation |
| `/cv check-agent` | Validate single agent definition | | `/cv check-agent` | Validate single agent definition |
@@ -16,3 +18,9 @@ Cross-plugin compatibility validation and agent verification.
| `/cv dependency-graph` | Mermaid visualization of plugin dependencies | | `/cv dependency-graph` | Mermaid visualization of plugin dependencies |
| `/cv setup` | Setup wizard for contract-validator MCP | | `/cv setup` | Setup wizard for contract-validator MCP |
| `/cv status` | Marketplace-wide health check | | `/cv status` | Marketplace-wide health check |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,14 +1,16 @@
--- ---
description: Data engineering tools with pandas, PostgreSQL, and dbt name: data
description: Data engineering tools — type /data <action> for commands
--- ---
# /data # /data
Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration. Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration.
When invoked without a sub-command, display available actions and ask which to run.
## Sub-commands ## Available Commands
| Sub-command | Description | | Command | Description |
|-------------|-------------| |-------------|-------------|
| `/data ingest` | Load data from CSV, Parquet, JSON into DataFrame | | `/data ingest` | Load data from CSV, Parquet, JSON into DataFrame |
| `/data profile` | Generate data profiling report with statistics | | `/data profile` | Generate data profiling report with statistics |
@@ -22,3 +24,9 @@ Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration.
| `/data review` | Comprehensive data integrity audits | | `/data review` | Comprehensive data integrity audits |
| `/data gate` | Binary pass/fail data integrity gates | | `/data gate` | Binary pass/fail data integrity gates |
| `/data setup` | Setup wizard for data-platform MCP servers | | `/data setup` | Setup wizard for data-platform MCP servers |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,17 +1,25 @@
--- ---
description: Test data generation — create realistic fake data from schema definitions name: seed
description: Test data generation — type /seed <action> for commands
--- ---
# /seed # /seed
Test data generation and database seeding with reproducible profiles. Test data generation and database seeding with reproducible profiles.
When invoked without a sub-command, display available actions and ask which to run.
## Sub-commands ## Available Commands
| Sub-command | Description | | Command | Description |
|-------------|-------------| |-------------|-------------|
| `/seed setup` | Setup wizard for data-seed configuration | | `/seed setup` | Setup wizard for data-seed configuration |
| `/seed generate` | Generate seed data from schema or models | | `/seed generate` | Generate seed data from schema or models |
| `/seed apply` | Apply seed data to database or create fixture files | | `/seed apply` | Apply seed data to database or create fixture files |
| `/seed profile` | Define reusable data profiles (small, medium, large) | | `/seed profile` | Define reusable data profiles (small, medium, large) |
| `/seed validate` | Validate seed data against schema constraints | | `/seed validate` | Validate seed data against schema constraints |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,17 +1,25 @@
--- ---
description: MCP debugging — inspect servers, test tools, view logs, scaffold new servers name: debug-mcp
description: MCP debugging — type /debug-mcp <action> for commands
--- ---
# /debug-mcp # /debug-mcp
MCP server debugging, inspection, and development toolkit. MCP server debugging, inspection, and development toolkit.
When invoked without a sub-command, display available actions and ask which to run.
## Sub-commands ## Available Commands
| Sub-command | Description | | Command | Description |
|-------------|-------------| |-------------|-------------|
| `/debug-mcp status` | Show all MCP servers with health status | | `/debug-mcp status` | Show all MCP servers with health status |
| `/debug-mcp test` | Test a specific MCP tool call | | `/debug-mcp test` | Test a specific MCP tool call |
| `/debug-mcp logs` | View recent MCP server logs and errors | | `/debug-mcp logs` | View recent MCP server logs and errors |
| `/debug-mcp inspect` | Inspect MCP server config and dependencies | | `/debug-mcp inspect` | Inspect MCP server config and dependencies |
| `/debug-mcp scaffold` | Generate MCP server skeleton project | | `/debug-mcp scaffold` | Generate MCP server skeleton project |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,17 +1,26 @@
--- ---
description: Documentation management and drift detection name: doc
description: Documentation management and drift detection — type /doc <action> for commands
--- ---
# /doc # /doc
Documentation management, drift detection, and synchronization. Documentation management, drift detection, and synchronization.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/doc audit` | Full documentation audit - scans for doc drift | | `/doc audit` | Full documentation audit - scans for doc drift |
| `/doc sync` | Synchronize pending documentation updates | | `/doc sync` | Synchronize pending documentation updates |
| `/doc changelog-gen` | Generate changelog from conventional commits | | `/doc changelog-gen` | Generate changelog from conventional commits |
| `/doc coverage` | Documentation coverage metrics by function/class | | `/doc coverage` | Documentation coverage metrics by function/class |
| `/doc stale-docs` | Flag documentation behind code changes | | `/doc stale-docs` | Flag documentation behind code changes |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,17 +1,27 @@
--- ---
description: Git workflow automation with safety enforcement name: gitflow
description: Git workflow automation with safety enforcement — type /gitflow <action> for commands
--- ---
# /gitflow # /gitflow
Git workflow automation with smart commits, branch management, and safety enforcement. Git workflow automation with smart commits, branch management, and safety enforcement.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/gitflow setup` | Configure git-flow for the current project |
| `/gitflow commit` | Smart commit with optional --push, --merge, --sync | | `/gitflow commit` | Smart commit with optional --push, --merge, --sync |
| `/gitflow branch-start` | Create a properly-named feature branch | | `/gitflow branch-start` | Create a properly-named feature branch |
| `/gitflow branch-cleanup` | Clean up merged/stale branches | | `/gitflow branch-cleanup` | Clean up merged/stale branches |
| `/gitflow status` | Enhanced git status with recommendations | | `/gitflow status` | Enhanced git status with recommendations |
| `/gitflow config` | Configure git-flow settings | | `/gitflow config` | Configure git-flow settings |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,18 +1,27 @@
--- ---
description: Deployment management — generate configs, validate pipelines, manage environments name: deploy
description: Deployment management — type /deploy <action> for commands
--- ---
# /deploy # /deploy
CI/CD deployment pipeline management for Docker Compose and self-hosted infrastructure. CI/CD deployment pipeline management for Docker Compose and self-hosted infrastructure.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/deploy setup` | Interactive setup wizard for deployment configuration | | `/deploy setup` | Interactive setup wizard for deployment configuration |
| `/deploy generate` | Generate docker-compose.yml, Caddyfile, and systemd units | | `/deploy generate` | Generate docker-compose.yml, Caddyfile, and systemd units |
| `/deploy validate` | Validate deployment configs for correctness and best practices | | `/deploy validate` | Validate deployment configs for correctness and best practices |
| `/deploy env` | Manage environment-specific config files (.env.development, .env.production) | | `/deploy env` | Manage environment-specific config files (.env.development, .env.production) |
| `/deploy check` | Pre-deployment health check (disk, memory, ports, DNS, Docker) | | `/deploy check` | Pre-deployment health check (disk, memory, ports, DNS, Docker) |
| `/deploy rollback` | Generate rollback plan for a deployment | | `/deploy rollback` | Generate rollback plan for a deployment |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,18 +1,27 @@
--- ---
description: Release management — version bumping, changelog updates, tag creation name: release
description: Release management — type /release <action> for commands
--- ---
# /release # /release
Release management with semantic versioning, changelog generation, and tag management. Release management with semantic versioning, changelog generation, and tag management.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/release setup` | Setup wizard — detect version locations and release conventions | | `/release setup` | Setup wizard — detect version locations and release conventions |
| `/release prepare` | Prepare release: bump versions, update changelog, create branch | | `/release prepare` | Prepare release: bump versions, update changelog, create branch |
| `/release validate` | Pre-release checks — verify versions, changelog, dependencies | | `/release validate` | Pre-release checks — verify versions, changelog, dependencies |
| `/release tag` | Create and push git tag with release notes | | `/release tag` | Create and push git tag with release notes |
| `/release rollback` | Revert a release — remove tag, revert version bump | | `/release rollback` | Revert a release — remove tag, revert version bump |
| `/release status` | Show current version and unreleased changes | | `/release status` | Show current version and unreleased changes |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,15 +1,18 @@
--- ---
description: Pull request review and management name: pr
description: Pull request review and management — type /pr <action> for commands
--- ---
# /pr # /pr
Multi-agent pull request review with confidence scoring. Multi-agent pull request review with confidence scoring.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/pr review` | Full multi-agent PR review with confidence scoring | | `/pr review` | Full multi-agent PR review with confidence scoring |
| `/pr summary` | Quick summary of PR changes | | `/pr summary` | Quick summary of PR changes |
| `/pr findings` | List and filter review findings by category/severity | | `/pr findings` | List and filter review findings by category/severity |
@@ -17,3 +20,9 @@ Multi-agent pull request review with confidence scoring.
| `/pr init` | Quick project setup for PR reviews | | `/pr init` | Quick project setup for PR reviews |
| `/pr sync` | Sync config with git remote after repo move/rename | | `/pr sync` | Sync config with git remote after repo move/rename |
| `/pr setup` | Setup wizard for pr-review | | `/pr setup` | Setup wizard for pr-review |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -0,0 +1,22 @@
---
name: hygiene
description: Project hygiene checks — type /hygiene <action> for commands
---
# /hygiene
Manual project hygiene checks for file organization and cleanup.
When invoked without a sub-command, display available actions and ask which to run.
## Available Commands
| Command | Description |
|---------|-------------|
| `/hygiene check` | Run project hygiene checks (temp files, misplaced files, empty dirs) |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,18 @@
--- ---
description: Architecture Decision Records management name: adr
description: Architecture Decision Records management — type /adr <action> for commands
--- ---
# /adr # /adr
## Sub-commands Architecture Decision Records management for projman.
| Sub-command | Description | When invoked without a sub-command, display available actions and ask which to run.
|-------------|-------------|
## Available Commands
| Command | Description |
|---------|-------------|
| `/adr create` | Create a new ADR wiki page | | `/adr create` | Create a new ADR wiki page |
| `/adr list` | List all ADRs by status | | `/adr list` | List all ADRs by status |
| `/adr update` | Update an existing ADR | | `/adr update` | Update an existing ADR |
@@ -21,3 +26,9 @@ description: Architecture Decision Records management
/adr update <ADR-NNNN> [--status accepted|deprecated] /adr update <ADR-NNNN> [--status accepted|deprecated]
/adr supersede <ADR-NNNN> --by <ADR-MMMM> /adr supersede <ADR-NNNN> --by <ADR-MMMM>
``` ```
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,22 @@
--- ---
description: Label management name: labels
description: Label management — type /labels <action> for commands
--- ---
# /labels # /labels
Label management for projman. Label management for projman.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/labels sync` | Sync label taxonomy to Gitea repository | | `/labels sync` | Sync label taxonomy to Gitea repository |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,18 @@
--- ---
description: Project lifecycle management — concept to MVP name: project
description: Project lifecycle management — type /project <action> for commands
--- ---
# /project # /project
## Sub-commands Project lifecycle management from concept to MVP.
| Sub-command | Description | When invoked without a sub-command, display available actions and ask which to run.
|-------------|-------------|
## Available Commands
| Command | Description |
|---------|-------------|
| `/project initiation` | Analyze source, create charter, decompose into epics | | `/project initiation` | Analyze source, create charter, decompose into epics |
| `/project plan` | Create WBS, risk register, sprint roadmap | | `/project plan` | Create WBS, risk register, sprint roadmap |
| `/project status` | Full project hierarchy view | | `/project status` | Full project hierarchy view |
@@ -21,3 +26,9 @@ description: Project lifecycle management — concept to MVP
/project status <project-name> /project status <project-name>
/project close <project-name> /project close <project-name>
``` ```
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,22 @@
--- ---
description: projman plugin management name: projman
description: projman plugin management — type /projman <action> for commands
--- ---
# /projman # /projman
Plugin-level management commands for projman. Plugin-level management commands for projman.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/projman setup` | Configure projman for a project | | `/projman setup` | Configure projman for a project |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,4 +1,5 @@
--- ---
name: rfc
description: RFC lifecycle management - create, list, review, approve, reject description: RFC lifecycle management - create, list, review, approve, reject
agent: planner agent: planner
--- ---
@@ -15,22 +16,30 @@ agent: planner
Manage the full RFC lifecycle through sub-commands. RFCs provide a structured way to document, discuss, and approve changes before implementation. Manage the full RFC lifecycle through sub-commands. RFCs provide a structured way to document, discuss, and approve changes before implementation.
When invoked without a sub-command, display available actions and ask which to run.
## Invocation ## Invocation
``` ```
/rfc <sub-command> [arguments] /rfc <sub-command> [arguments]
``` ```
### Sub-Commands ## Available Commands
| Sub-Command | Usage | Description | | Command | Usage | Description |
|-------------|-------|-------------| |---------|-------|-------------|
| `create` | `/rfc create` | Create new RFC from conversation or clarified spec | | `create` | `/rfc create` | Create new RFC from conversation or clarified spec |
| `list` | `/rfc list [filter]` | List all RFCs grouped by status | | `list` | `/rfc list [filter]` | List all RFCs grouped by status |
| `review` | `/rfc review <number>` | Submit Draft RFC for review | | `review` | `/rfc review <number>` | Submit Draft RFC for review |
| `approve` | `/rfc approve <number>` | Approve RFC in Review status | | `approve` | `/rfc approve <number>` | Approve RFC in Review status |
| `reject` | `/rfc reject <number>` | Reject RFC with documented reason | | `reject` | `/rfc reject <number>` | Reject RFC with documented reason |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command
--- ---
## Sub-Command: create ## Sub-Command: create

View File

@@ -1,18 +1,27 @@
--- ---
description: Sprint lifecycle management name: sprint
description: Sprint lifecycle management — type /sprint <action> for commands
--- ---
# /sprint # /sprint
Sprint lifecycle management for projman. Sprint lifecycle management for projman.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/sprint plan` | Analyze requirements, create issues, request approval | | `/sprint plan` | Analyze requirements, create issues, request approval |
| `/sprint start` | Begin execution, load context, dispatch tasks | | `/sprint start` | Begin execution, load context, dispatch tasks |
| `/sprint status` | Check progress, blockers, completion percentage | | `/sprint status` | Check progress, blockers, completion percentage |
| `/sprint close` | Capture lessons learned, close milestone | | `/sprint close` | Capture lessons learned, close milestone |
| `/sprint review` | Pre-close code quality review | | `/sprint review` | Pre-close code quality review |
| `/sprint test` | Run/generate tests for sprint scope | | `/sprint test` | Run/generate tests for sprint scope |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,19 +1,27 @@
--- ---
name: api name: api
description: API development toolkit — route scaffolding, OpenAPI validation, middleware management description: API development toolkit — type /api <action> for commands
--- ---
# /api # /api
REST and GraphQL API scaffolding, validation, and documentation for FastAPI and Express. REST and GraphQL API scaffolding, validation, and documentation for FastAPI and Express.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/api setup` | Setup wizard for saas-api-platform | | `/api setup` | Setup wizard for saas-api-platform |
| `/api scaffold` | Generate routes, models, and schemas | | `/api scaffold` | Generate routes, models, and schemas |
| `/api validate` | Validate routes against OpenAPI spec | | `/api validate` | Validate routes against OpenAPI spec |
| `/api docs` | Generate or update OpenAPI specification | | `/api docs` | Generate or update OpenAPI specification |
| `/api test-routes` | Generate test cases for API endpoints | | `/api test-routes` | Generate test cases for API endpoints |
| `/api middleware` | Add and configure middleware | | `/api middleware` | Add and configure middleware |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,19 +1,27 @@
--- ---
name: db-migrate name: db-migrate
description: Database migration toolkit — generate, validate, and manage schema migrations description: Database migration toolkit — type /db-migrate <action> for commands
--- ---
# /db-migrate # /db-migrate
Database migration management for Alembic, Prisma, and raw SQL. Database migration management for Alembic, Prisma, and raw SQL.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/db-migrate setup` | Setup wizard for migration tool detection | | `/db-migrate setup` | Setup wizard for migration tool detection |
| `/db-migrate generate` | Generate migration from model diff | | `/db-migrate generate` | Generate migration from model diff |
| `/db-migrate validate` | Check migration safety | | `/db-migrate validate` | Check migration safety |
| `/db-migrate plan` | Show execution plan with rollback strategy | | `/db-migrate plan` | Show execution plan with rollback strategy |
| `/db-migrate history` | Display migration history | | `/db-migrate history` | Display migration history |
| `/db-migrate rollback` | Generate rollback migration | | `/db-migrate rollback` | Generate rollback migration |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,18 +1,27 @@
--- ---
description: React development toolkit — component scaffolding, routing, state management, and linting name: react
description: React development toolkit — type /react <action> for commands
--- ---
# /react # /react
React frontend development toolkit with component scaffolding, routing, state management, and anti-pattern detection. React frontend development toolkit with component scaffolding, routing, state management, and anti-pattern detection.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/react setup` | Setup wizard for React project detection and configuration | | `/react setup` | Setup wizard for React project detection and configuration |
| `/react component` | Scaffold component with props, types, and tests | | `/react component` | Scaffold component with props, types, and tests |
| `/react route` | Add route with page component and error boundary | | `/react route` | Add route with page component and error boundary |
| `/react state` | Set up state management pattern (Context, Zustand, Redux Toolkit) | | `/react state` | Set up state management pattern (Context, Zustand, Redux Toolkit) |
| `/react hook` | Generate custom hook with types and tests | | `/react hook` | Generate custom hook with types and tests |
| `/react lint` | Validate component tree and detect anti-patterns | | `/react lint` | Validate component tree and detect anti-patterns |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,18 +1,27 @@
--- ---
description: Test automation — generate tests, analyze coverage, manage fixtures name: test
description: Test automation — type /test <action> for commands
--- ---
# /test # /test
Test automation toolkit for unit, integration, and end-to-end testing. Test automation toolkit for unit, integration, and end-to-end testing.
## Sub-commands When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description | ## Available Commands
|-------------|-------------|
| Command | Description |
|---------|-------------|
| `/test setup` | Setup wizard — detect framework, configure test runner | | `/test setup` | Setup wizard — detect framework, configure test runner |
| `/test generate` | Generate test cases for functions, classes, or modules | | `/test generate` | Generate test cases for functions, classes, or modules |
| `/test coverage` | Analyze coverage and identify untested paths | | `/test coverage` | Analyze coverage and identify untested paths |
| `/test fixtures` | Generate or manage test fixtures and mocks | | `/test fixtures` | Generate or manage test fixtures and mocks |
| `/test e2e` | Generate end-to-end test scenarios | | `/test e2e` | Generate end-to-end test scenarios |
| `/test run` | Run tests with formatted output | | `/test run` | Run tests with formatted output |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,14 +1,16 @@
--- ---
description: Visualization tools with DMC validation, charts, and theming name: viz
description: Visualization tools — type /viz <action> for commands
--- ---
# /viz # /viz
Visualization tools with Dash Mantine Components validation, Plotly charts, and theming. Visualization tools with Dash Mantine Components validation, Plotly charts, and theming.
When invoked without a sub-command, display available actions and ask which to run.
## Sub-commands ## Available Commands
| Sub-command | Description | | Command | Description |
|-------------|-------------| |-------------|-------------|
| `/viz theme` | Apply existing theme to visualizations | | `/viz theme` | Apply existing theme to visualizations |
| `/viz theme-new` | Create new custom theme with design tokens | | `/viz theme-new` | Create new custom theme with design tokens |
@@ -22,3 +24,9 @@ Visualization tools with Dash Mantine Components validation, Plotly charts, and
| `/viz design-review` | Detailed design system audits | | `/viz design-review` | Detailed design system audits |
| `/viz design-gate` | Binary pass/fail design system validation | | `/viz design-gate` | Binary pass/fail design system validation |
| `/viz setup` | Setup wizard for viz-platform MCP server | | `/viz setup` | Setup wizard for viz-platform MCP server |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command