personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: update internal command references in all plugin files

Browse Source 
Updated:
- projman: 4 commands + 4 skills + integration snippet
- git-flow: 4 commands + 3 skills + integration snippet
- pr-review: 1 command cross-reference
- cmdb-assistant: 1 command + 1 skill
- data-platform: 8 commands + integration snippet
- viz-platform: 11 commands + integration snippet
- contract-validator: 1 command + 1 skill + 1 agent

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Leo Miranda
2026-02-03 21:16:00 -05:00
parent 71f1f3239a
commit 4ba38eb620
45 changed files with 200 additions and 162 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
plugins/cmdb-assistant/commands/cmdb-setup.md
View File

@@ -18,7 +18,7 @@ Configure the cmdb-assistant plugin with NetBox integration.
## Usage
```
/initial-setup
/cmdb-setup
```
## Instructions

2
plugins/cmdb-assistant/skills/visual-header.md
View File

@@ -24,7 +24,7 @@ Standard visual header for cmdb-assistant commands.
| `/cmdb-topology` | Topology |
| `/change-audit` | Change Audit |
| `/ip-conflicts` | IP Conflict Detection |
| `/initial-setup` | Setup Wizard |
| `/cmdb-setup` | Setup Wizard |
| Agent mode | Infrastructure Management |
## Usage

2
plugins/contract-validator/agents/full-validation.md
View File

@@ -100,5 +100,5 @@ You are a contract validation specialist. Your role is to perform comprehensive
2. Parses all README.md files
3. Runs 66 pairwise compatibility checks
4. Finds 3 errors, 4 warnings
5. Reports: "Command conflict: projman and data-platform both define /initial-setup"
5. Reports: "Command conflict: pluginA and pluginB both define /setup"
6. Suggests: "Rename one command to avoid ambiguity"

2
plugins/contract-validator/commands/cv-setup.md
View File

@@ -2,7 +2,7 @@
description: Interactive setup wizard for contract-validator plugin
---
# /initial-setup - Contract-Validator Setup Wizard
# /cv-setup - Contract Validator Setup Wizard
## Skills to Load
- skills/visual-output.md

2
plugins/contract-validator/skills/mcp-tools-reference.md
View File

@@ -65,6 +65,6 @@ Available MCP tools for contract-validator operations.
## Error Handling
If MCP tools fail:
1. Check if `/initial-setup` has been run
1. Check if `/cv-setup` has been run
2. Verify session was restarted after setup
3. Check MCP server venv exists and is valid

32
plugins/data-platform/claude-md-integration.md
View File

@@ -18,12 +18,12 @@ This project uses the data-platform plugin for data engineering workflows.
| Command | Purpose |
|---------|---------|
| `/ingest` | Load data from files or database |
| `/profile` | Generate statistical profile |
| `/schema` | Show schema information |
| `/explain` | Explain dbt model |
| `/lineage` | Show data lineage |
| `/run` | Execute dbt models |
| `/data-ingest` | Load data from files or database |
| `/data-profile` | Generate statistical profile |
| `/data-schema` | Show schema information |
| `/data-explain` | Explain dbt model |
| `/data-lineage` | Show data lineage |
| `/data-run` | Execute dbt models |
### data_ref Convention
@@ -36,9 +36,9 @@ DataFrames are stored with references. Use meaningful names:
### dbt Workflow
1. Always validate before running: `/run` includes automatic `dbt_parse`
1. Always validate before running: `/data-run` includes automatic `dbt_parse`
2. For dbt 1.9+, check for deprecated syntax before commits
3. Use `/lineage` to understand impact of changes
3. Use `/data-lineage` to understand impact of changes
### Database Access
@@ -69,22 +69,22 @@ DATA_PLATFORM_MAX_ROWS=100000
### Data Exploration
```
/ingest data/raw_customers.csv
/profile raw_customers
/schema
/data-ingest data/raw_customers.csv
/data-profile raw_customers
/data-schema
```
### ETL Development
```
/schema orders # Understand source
/explain stg_orders # Understand transformation
/run stg_orders # Test the model
/lineage fct_orders # Check downstream impact
/data-schema orders # Understand source
/data-explain stg_orders # Understand transformation
/data-run stg_orders # Test the model
/data-lineage fct_orders # Check downstream impact
```
### Database Analysis
```
/schema # List all tables
/data-schema # List all tables
pg_columns orders # Detailed schema
st_tables # Find spatial data
```

8
plugins/data-platform/commands/data-explain.md
View File

@@ -1,4 +1,4 @@
# /explain - dbt Model Explanation
# /data-explain - dbt Model Explanation
## Skills to Load
- skills/dbt-workflow.md
@@ -13,7 +13,7 @@ Display header: `DATA-PLATFORM - Model Explanation`
## Usage
```
/explain <model_name>
/data-explain <model_name>
```
## Workflow
@@ -26,8 +26,8 @@ Display header: `DATA-PLATFORM - Model Explanation`
## Examples
```
/explain dim_customers
/explain fct_orders
/data-explain dim_customers
/data-explain fct_orders
```
## Required MCP Tools

10
plugins/data-platform/commands/data-ingest.md
View File

@@ -1,4 +1,4 @@
# /ingest - Data Ingestion
# /data-ingest - Data Ingestion
## Skills to Load
- skills/mcp-tools-reference.md
@@ -11,7 +11,7 @@ Display header: `DATA-PLATFORM - Ingest`
## Usage
```
/ingest [source]
/data-ingest [source]
```
## Workflow
@@ -31,9 +31,9 @@ Display header: `DATA-PLATFORM - Ingest`
## Examples
```
/ingest data/sales.csv
/ingest data/customers.parquet
/ingest "SELECT * FROM orders WHERE created_at > '2024-01-01'"
/data-ingest data/sales.csv
/data-ingest data/customers.parquet
/data-ingest "SELECT * FROM orders WHERE created_at > '2024-01-01'"
```
## Required MCP Tools

8
plugins/data-platform/commands/data-lineage.md
View File

@@ -1,4 +1,4 @@
# /lineage - Data Lineage Visualization
# /data-lineage - Data Lineage Visualization
## Skills to Load
- skills/lineage-analysis.md
@@ -12,7 +12,7 @@ Display header: `DATA-PLATFORM - Lineage`
## Usage
```
/lineage <model_name> [--depth N]
/data-lineage <model_name> [--depth N]
```
## Workflow
@@ -25,8 +25,8 @@ Display header: `DATA-PLATFORM - Lineage`
## Examples
```
/lineage dim_customers
/lineage fct_orders --depth 3
/data-lineage dim_customers
/data-lineage fct_orders --depth 3
```
## Required MCP Tools

8
plugins/data-platform/commands/data-profile.md
View File

@@ -1,4 +1,4 @@
# /profile - Data Profiling
# /data-profile - Data Profiling
## Skills to Load
- skills/data-profiling.md
@@ -12,7 +12,7 @@ Display header: `DATA-PLATFORM - Data Profile`
## Usage
```
/profile <data_ref>
/data-profile <data_ref>
```
## Workflow
@@ -27,8 +27,8 @@ Execute `skills/data-profiling.md` profiling workflow:
## Examples
```
/profile sales_data
/profile df_a1b2c3d4
/data-profile sales_data
/data-profile df_a1b2c3d4
```
## Required MCP Tools

4
plugins/data-platform/commands/data-review.md
View File

@@ -145,5 +145,5 @@ Use `/data-gate` when you want to automate.
## Related Commands
- `/data-gate` - Binary pass/fail for automation
- `/lineage` - Visualize dbt model dependencies
- `/schema` - Explore database schema
- `/data-lineage` - Visualize dbt model dependencies
- `/data-schema` - Explore database schema

14
plugins/data-platform/commands/data-run.md
View File

@@ -1,4 +1,4 @@
# /run - Execute dbt Models
# /data-run - Execute dbt Models
## Skills to Load
- skills/dbt-workflow.md
@@ -12,7 +12,7 @@ Display header: `DATA-PLATFORM - dbt Run`
## Usage
```
/run [model_selection] [--full-refresh]
/data-run [model_selection] [--full-refresh]
```
## Workflow
@@ -30,11 +30,11 @@ See `skills/dbt-workflow.md` for full selection patterns.
## Examples
```
/run # Run all models
/run dim_customers # Run specific model
/run +fct_orders # Run model and upstream
/run tag:daily # Run models with tag
/run --full-refresh # Rebuild incremental models
/data-run # Run all models
/data-run dim_customers # Run specific model
/data-run +fct_orders # Run model and upstream
/data-run tag:daily # Run models with tag
/data-run --full-refresh # Rebuild incremental models
```
## Required MCP Tools

10
plugins/data-platform/commands/data-schema.md
View File

@@ -1,4 +1,4 @@
# /schema - Schema Exploration
# /data-schema - Schema Exploration
## Skills to Load
- skills/mcp-tools-reference.md
@@ -11,7 +11,7 @@ Display header: `DATA-PLATFORM - Schema Explorer`
## Usage
```
/schema [table_name | data_ref]
/data-schema [table_name | data_ref]
```
## Workflow
@@ -30,9 +30,9 @@ Display header: `DATA-PLATFORM - Schema Explorer`
## Examples
```
/schema # List all tables and DataFrames
/schema customers # Show table schema
/schema sales_data # Show DataFrame schema
/data-schema # List all tables and DataFrames
/data-schema customers # Show table schema
/data-schema sales_data # Show DataFrame schema
```
## Required MCP Tools

4
plugins/data-platform/commands/data-setup.md
View File

@@ -1,4 +1,4 @@
# /initial-setup - Data Platform Setup Wizard
# /data-setup - Data Platform Setup Wizard
## Skills to Load
- skills/setup-workflow.md
@@ -11,7 +11,7 @@ Display header: `DATA-PLATFORM - Setup Wizard`
## Usage
```
/initial-setup
/data-setup
```
## Workflow

6
plugins/git-flow/claude-md-integration.md
View File

@@ -40,9 +40,9 @@ Use conventional commits:
| Command | Use Case |
|---------|----------|
| `/commit` | Create commit with smart message |
| `/commit-push` | Commit and push |
| `/commit-merge` | Commit and merge to base |
| `/git-commit` | Create commit with smart message |
| `/git-commit-push` | Commit and push |
| `/git-commit-merge` | Commit and merge to base |
| `/branch-start` | Start new branch |
| `/git-status` | Enhanced status |

6
plugins/git-flow/commands/git-commit-merge.md
View File

@@ -1,10 +1,10 @@
---
name: commit-merge
name: git-commit-merge
description: Commit current changes and merge branch into target
agent: git-assistant
---
# /commit-merge - Commit and Merge
# /git-commit-merge - Commit and Merge
## Skills
@@ -29,7 +29,7 @@ Commit current changes, then merge the current branch into a target branch.
## Workflow
1. **Display header** - Show GIT-FLOW Commit & Merge header
2. **Run /commit** - Execute standard commit workflow
2. **Run /git-commit** - Execute standard commit workflow
3. **Identify target** - Prompt for target branch if not specified
4. **Select strategy** - Merge commit, squash, or rebase (per merge-workflow.md)
5. **Execute merge** - Switch to target, pull, merge, push

6
plugins/git-flow/commands/git-commit-push.md
View File

@@ -1,10 +1,10 @@
---
name: commit-push
name: git-commit-push
description: Create a commit and push to remote in one operation
agent: git-assistant
---
# /commit-push - Commit and Push
# /git-commit-push - Commit and Push
## Skills
@@ -28,7 +28,7 @@ Create a commit and push to the remote repository in one operation.
## Workflow
1. **Display header** - Show GIT-FLOW Commit & Push header
2. **Run /commit** - Execute standard commit workflow
2. **Run /git-commit** - Execute standard commit workflow
3. **Check upstream** - Set up tracking if needed (`git push -u`)
4. **Push** - Push to remote
5. **Handle conflicts** - Offer rebase/merge/force if push fails (per sync-workflow.md)

6
plugins/git-flow/commands/git-commit-sync.md
View File

@@ -1,10 +1,10 @@
---
name: commit-sync
name: git-commit-sync
description: Commit, push, and sync with base branch
agent: git-assistant
---
# /commit-sync - Commit, Push, and Sync
# /git-commit-sync - Commit, Push, and Sync
## Skills
@@ -28,7 +28,7 @@ Full sync operation: commit local changes, push to remote, sync with upstream/ba
## Workflow
1. **Display header** - Show GIT-FLOW Commit Sync header
2. **Run /commit** - Execute standard commit workflow
2. **Run /git-commit** - Execute standard commit workflow
3. **Push to remote** - Push committed changes
4. **Fetch with prune** - `git fetch --all --prune`
5. **Sync with base** - Rebase on base branch (per sync-workflow.md)

4
plugins/git-flow/commands/git-commit.md
View File

@@ -1,10 +1,10 @@
---
name: commit
name: git-commit
description: Create a git commit with auto-generated conventional commit message
agent: git-assistant
---
# /commit - Smart Commit
# /git-commit - Smart Commit
## Skills

2
plugins/git-flow/skills/commit-conventions.md
View File

@@ -6,7 +6,7 @@ Defines conventional commit message format for consistent, parseable commit hist
## When to Use
- Generating commit messages in `/commit`
- Generating commit messages in `/git-commit`
- Validating user-provided commit messages
- Explaining commit format to users

2
plugins/git-flow/skills/merge-workflow.md
View File

@@ -6,7 +6,7 @@ Defines merge strategies, conflict resolution approaches, and post-merge cleanup
## When to Use
- Merging feature branches in `/commit-merge`
- Merging feature branches in `/git-commit-merge`
- Resolving conflicts during sync operations
- Cleaning up after successful merges

4
plugins/git-flow/skills/sync-workflow.md
View File

@@ -6,8 +6,8 @@ Defines push/pull patterns, rebase strategies, upstream tracking, and stale bran
## When to Use
- Pushing commits in `/commit-push`
- Full sync operations in `/commit-sync`
- Pushing commits in `/git-commit-push`
- Full sync operations in `/git-commit-sync`
- Detecting and reporting stale branches
## Push Workflow

4
plugins/pr-review/commands/project-init.md
View File

@@ -17,13 +17,13 @@ Display header: `PR-REVIEW - Project Setup`
Fast setup when system-level config already exists.
**Use when:** Already ran `/initial-setup`, starting new project
**Use when:** Already ran `/pr-setup`, starting new project
## Workflow
### Pre-Flight Check
Verify `~/.config/claude/gitea.env` exists. If missing: redirect to `/initial-setup`
Verify `~/.config/claude/gitea.env` exists. If missing: redirect to `/pr-setup`
### Project Setup

2
plugins/projman/claude-md-integration.md
View File

@@ -11,7 +11,7 @@ This project uses the **projman** plugin for sprint planning and project managem
| `/sprint-status` | Check current sprint progress and identify blockers |
| `/sprint-close` | Complete sprint and capture lessons learned to Gitea Wiki |
| `/labels-sync` | Synchronize label taxonomy from Gitea |
| `/initial-setup` | Run initial setup for projman plugin |
| `/pm-setup` | Run initial setup for projman plugin |
| `/rfc create` | Create new RFC from conversation or clarified spec |
| `/rfc list` | List all RFCs grouped by status |
| `/rfc review` | Submit Draft RFC for review |

8
plugins/projman/commands/pm-debug.md
View File

@@ -2,7 +2,7 @@
description: Diagnose issues and create reports, or investigate existing diagnostic issues
---
# Debug
# PM Debug
## Skills Required
@@ -17,9 +17,9 @@ Unified debugging command for diagnostics and issue investigation.
## Invocation
```
/debug # Ask which mode
/debug report # Run diagnostics, create issue
/debug review # Investigate existing issues
/pm-debug # Ask which mode
/pm-debug report # Run diagnostics, create issue
/pm-debug review # Investigate existing issues
```
## Mode Selection

4
plugins/projman/commands/pm-review.md
View File

@@ -3,7 +3,7 @@ description: Pre-sprint-close code quality review
agent: code-reviewer
---
# Code Review for Sprint Close
# PM Review - Code Review for Sprint Close
## Skills Required
@@ -16,7 +16,7 @@ Review recent code changes for quality issues before closing the sprint.
## Invocation
Run `/review` before `/sprint-close` to catch issues.
Run `/pm-review` before `/sprint-close` to catch issues.
## Workflow

12
plugins/projman/commands/pm-setup.md
View File

@@ -2,7 +2,7 @@
description: Configure projman - full setup, quick project init, or sync after repo move
---
# Setup
# PM Setup
## Skills Required
@@ -22,11 +22,11 @@ Unified setup command for all configuration needs.
## Invocation
```
/setup # Auto-detect appropriate mode
/setup --full # Full wizard (MCP + system + project)
/setup --quick # Project-only setup
/setup --sync # Update after repo move
/setup --clear-cache # Clear plugin cache (between sessions only)
/pm-setup # Auto-detect appropriate mode
/pm-setup --full # Full wizard (MCP + system + project)
/pm-setup --quick # Project-only setup
/pm-setup --sync # Update after repo move
/pm-setup --clear-cache # Clear plugin cache (between sessions only)
```
## Mode Detection

34
plugins/projman/commands/pm-test.md
View File

@@ -2,7 +2,7 @@
description: Run tests with coverage or generate tests for specified code
---
# Test
# PM Test
## Skills Required
@@ -15,13 +15,13 @@ Unified testing command for running tests and generating new tests.
## Invocation
```
/test # Default: run tests
/test run # Run tests, check coverage
/test run --coverage # Run with coverage report
/test run --verbose # Verbose output
/test gen <target> # Generate tests for target
/test gen <target> --type=unit # Specific test type
/test gen <target> --framework=jest # Specific framework
/pm-test # Default: run tests
/pm-test run # Run tests, check coverage
/pm-test run --coverage # Run with coverage report
/pm-test run --verbose # Verbose output
/pm-test gen <target> # Generate tests for target
/pm-test gen <target> --type=unit # Specific test type
/pm-test gen <target> --framework=jest # Specific framework
```
## Mode Selection
@@ -104,15 +104,15 @@ See `skills/test-standards.md` for test patterns and structure.
## Sprint Integration
The `/test` command plays a critical role in the sprint close workflow:
The `/pm-test` command plays a critical role in the sprint close workflow:
1. After `/review` identifies code quality issues
1. After `/pm-review` identifies code quality issues
2. Before `/sprint-close` finalizes the sprint
3. The code reviewer and orchestrator reference test results when deciding if a sprint is ready to close
### Pre-Close Verification
When running `/test run` before sprint close:
When running `/pm-test run` before sprint close:
1. **Identify sprint files** - Files changed in the current sprint (via git diff against development)
2. **Check test coverage** - Report which sprint files have tests and which don't
@@ -125,31 +125,31 @@ When running `/test run` before sprint close:
### Run all tests
```
/test run
/pm-test run
```
Detects framework, runs full test suite, reports results.
### Run with coverage
```
/test run --coverage
/pm-test run --coverage
```
Same as above plus coverage percentage per file.
### Generate tests for a specific file
```
/test gen src/auth/jwt_service.py
/pm-test gen src/auth/jwt_service.py
```
Analyzes the file, generates a test file at `tests/test_jwt_service.py`.
### Generate specific test type
```
/test gen src/api/routes/auth.py --type=integration
/pm-test gen src/api/routes/auth.py --type=integration
```
Generates integration tests (request/response patterns) instead of unit tests.
### Generate with specific framework
```
/test gen src/components/Card.jsx --framework=vitest
/pm-test gen src/components/Card.jsx --framework=vitest
```
Uses Vitest instead of auto-detected framework.
@@ -161,7 +161,7 @@ Uses Vitest instead of auto-detected framework.
|----------|----------|
| No test framework detected | List what was checked, ask user to specify test command |
| Tests fail | Report failures clearly, recommend "TESTS MUST PASS before sprint close" |
| No tests exist for sprint files | Warn with file list, offer to generate with `/test gen` |
| No tests exist for sprint files | Warn with file list, offer to generate with `/pm-test gen` |
| External services required | Ask for confirmation before running tests that need database/API |
| Mixed framework project | Detect all frameworks, ask which to run or run all |

2
plugins/projman/skills/review-checklist.md
View File

@@ -12,7 +12,7 @@ Defines code review criteria, severity classification, and output format.
## When to Use
- **Code Reviewer agent**: During pre-sprint-close review
- **Commands**: `/review`
- **Commands**: `/pm-review`
---

2
plugins/projman/skills/setup-workflows.md
View File

@@ -1,6 +1,6 @@
# Setup Workflows
Shared workflows for the `/setup` command modes.
Shared workflows for the `/pm-setup` command modes.
## Mode Detection Logic

8
plugins/projman/skills/sprint-lifecycle.md
View File

@@ -20,7 +20,7 @@ Defines the valid sprint lifecycle states and transitions, enforced via labels o
```
idle -> Sprint/Planning -> Sprint/Executing -> Sprint/Reviewing -> idle
(sprint-plan) (sprint-start) (review) (sprint-close)
(sprint-plan) (sprint-start) (pm-review) (sprint-close)
```
## State Labels
@@ -30,7 +30,7 @@ idle -> Sprint/Planning -> Sprint/Executing -> Sprint/Reviewing -> idle
| *(no Sprint/* label)* | `/sprint-close` or initial state | Idle - no active sprint phase |
| `Sprint/Planning` | `/sprint-plan` | Planning in progress |
| `Sprint/Executing` | `/sprint-start` | Execution in progress |
| `Sprint/Reviewing` | `/review` | Code review in progress |
| `Sprint/Reviewing` | `/pm-review` | Code review in progress |
**Rule:** Only ONE `Sprint/*` label may exist on a milestone at a time. Setting a new one removes the previous one.
@@ -42,8 +42,8 @@ idle -> Sprint/Planning -> Sprint/Executing -> Sprint/Reviewing -> idle
|---------|---------------|------------|----------------|
| `/sprint-plan` | idle (no Sprint/* label) | `Sprint/Planning` | Warn: "Sprint is in [state]. Run `/sprint-close` first or use `--force` to re-plan." Allow with `--force`. |
| `/sprint-start` | `Sprint/Planning` | `Sprint/Executing` | Warn: "Expected Sprint/Planning state but found [state]. Run `/sprint-plan` first or use `--force`." Allow with `--force`. |
| `/review` | `Sprint/Executing` | `Sprint/Reviewing` | Warn: "Expected Sprint/Executing state but found [state]." Allow with `--force`. |
| `/sprint-close` | `Sprint/Reviewing` | Remove all Sprint/* labels (idle) | Warn: "Expected Sprint/Reviewing state but found [state]. Run `/review` first or use `--force`." Allow with `--force`. |
| `/pm-review` | `Sprint/Executing` | `Sprint/Reviewing` | Warn: "Expected Sprint/Executing state but found [state]." Allow with `--force`. |
| `/sprint-close` | `Sprint/Reviewing` | Remove all Sprint/* labels (idle) | Warn: "Expected Sprint/Reviewing state but found [state]. Run `/pm-review` first or use `--force`." Allow with `--force`. |
| `/sprint-status` | Any | No change (read-only) | Display current state in output. |
---

6
plugins/projman/skills/visual-output.md
View File

@@ -41,12 +41,12 @@ For commands that don't invoke a specific agent phase:
| Command | Phase Emoji | Phase Name |
|---------|-------------|------------|
| `/sprint-status` | 📊 Chart | STATUS |
| `/setup` | ⚙️ Gear | SETUP |
| `/debug` | 🐛 Bug | DEBUG |
| `/pm-setup` | ⚙️ Gear | SETUP |
| `/pm-debug` | 🐛 Bug | DEBUG |
| `/labels-sync` | 🏷️ Label | LABELS |
| `/suggest-version` | 📦 Package | VERSION |
| `/proposal-status` | 📋 Clipboard | PROPOSALS |
| `/test` | 🧪 Flask | TEST |
| `/pm-test` | 🧪 Flask | TEST |
| `/rfc` | 📄 Document | RFC [Sub-Command] |
---

16
plugins/viz-platform/claude-md-integration.md
View File

@@ -10,12 +10,12 @@ Add this snippet to your project's CLAUDE.md to enable viz-platform capabilities
This project uses viz-platform for Dash Mantine Components dashboards.
### Available Commands
- `/component {name}` - Inspect DMC component props
- `/chart {type}` - Create Plotly charts (line, bar, scatter, pie, area, histogram, box, heatmap, sunburst, treemap)
- `/dashboard {template}` - Create layouts (basic, sidebar, tabs, split)
- `/theme {name}` - Apply a theme
- `/theme-new {name}` - Create custom theme
- `/theme-css {name}` - Export theme as CSS
- `/viz-component {name}` - Inspect DMC component props
- `/viz-chart {type}` - Create Plotly charts (line, bar, scatter, pie, area, histogram, box, heatmap, sunburst, treemap)
- `/viz-dashboard {template}` - Create layouts (basic, sidebar, tabs, split)
- `/viz-theme {name}` - Apply a theme
- `/viz-theme-new {name}` - Create custom theme
- `/viz-theme-css {name}` - Export theme as CSS
### MCP Tools Available
- **DMC**: list_components, get_component_props, validate_component
@@ -49,8 +49,8 @@ If using with data-platform, add this section:
- `/profile {data_ref}` - Statistical summary
### Visualization (viz-platform)
- `/chart {type}` - Create charts from loaded data
- `/dashboard {template}` - Build dashboard layouts
- `/viz-chart {type}` - Create charts from loaded data
- `/viz-dashboard {template}` - Build dashboard layouts
### Workflow Pattern
1. Load data: `read_csv("data.csv")` → returns `data_ref`

4
plugins/viz-platform/commands/accessibility-check.md
View File

@@ -41,5 +41,5 @@ accessibility_validate_theme(theme_name="corporate")
## Related Commands
- `/theme-new {name}` - Create accessible theme
- `/chart {type}` - Create chart (check colors after)
- `/viz-theme-new {name}` - Create accessible theme
- `/viz-chart {type}` - Create chart (check colors after)

4
plugins/viz-platform/commands/design-review.md
View File

@@ -61,8 +61,8 @@ Each finding includes:
## Related Commands
- `/design-gate` - Binary pass/fail for sprint execution (no detailed report)
- `/component` - Inspect individual DMC component props
- `/theme` - Check active theme configuration
- `/viz-component` - Inspect individual DMC component props
- `/viz-theme` - Check active theme configuration
## Requirements

10
plugins/viz-platform/commands/viz-breakpoints.md
View File

@@ -2,7 +2,7 @@
description: Configure responsive breakpoints for dashboard layouts
---
# Configure Breakpoints
# Viz Breakpoints
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Configure responsive breakpoints for mobile-first design across screen sizes.
## Usage
```
/breakpoints {layout_ref}
/viz-breakpoints {layout_ref}
```
## Arguments
@@ -30,7 +30,7 @@ Configure responsive breakpoints for mobile-first design across screen sizes.
## Workflow
1. **User invokes**: `/breakpoints my-dashboard`
1. **User invokes**: `/viz-breakpoints my-dashboard`
2. **Agent asks**: Which breakpoints to customize? (shows current settings)
3. **Agent asks**: Mobile column count? (xs, typically 1-2)
4. **Agent asks**: Tablet column count? (md, typically 4-6)
@@ -39,5 +39,5 @@ Configure responsive breakpoints for mobile-first design across screen sizes.
## Related Commands
- `/dashboard {template}` - Create layout with default breakpoints
- `/theme {name}` - Theme includes default spacing values
- `/viz-dashboard {template}` - Create layout with default breakpoints
- `/viz-theme {name}` - Theme includes default spacing values

8
plugins/viz-platform/commands/viz-chart-export.md
View File

@@ -2,7 +2,7 @@
description: Export a Plotly chart to PNG, SVG, or PDF format
---
# Export Chart
# Viz Chart Export
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Export a Plotly chart to static image formats.
## Usage
```
/chart-export {format}
/viz-chart-export {format}
```
## Arguments
@@ -38,5 +38,5 @@ Requires `kaleido` package: `pip install kaleido`
## Related Commands
- `/chart {type}` - Create a chart
- `/theme {name}` - Apply theme before export
- `/viz-chart {type}` - Create a chart
- `/viz-theme {name}` - Apply theme before export

10
plugins/viz-platform/commands/viz-chart.md
View File

@@ -2,7 +2,7 @@
description: Create a Plotly chart with theme integration
---
# Create Chart
# Viz Chart
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Create a Plotly chart with automatic theme token application.
## Usage
```
/chart {type}
/viz-chart {type}
```
## Arguments
@@ -36,6 +36,6 @@ chart_create(chart_type="line", data_ref="df", x="date", y="value", theme=None)
## Related Commands
- `/chart-export {format}` - Export chart to image
- `/theme {name}` - Apply theme to charts
- `/dashboard` - Create layout with charts
- `/viz-chart-export {format}` - Export chart to image
- `/viz-theme {name}` - Apply theme to charts
- `/viz-dashboard` - Create layout with charts

8
plugins/viz-platform/commands/viz-component.md
View File

@@ -2,7 +2,7 @@
description: Inspect Dash Mantine Component props and validation
---
# Inspect Component
# Viz Component
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Inspect a DMC component's props, types, and defaults.
## Usage
```
/component {name}
/viz-component {name}
```
## Arguments
@@ -38,5 +38,5 @@ validate_component(component="Button", props={"variant": "filled"})
## Related Commands
- `/chart {type}` - Create charts
- `/dashboard {template}` - Create layouts
- `/viz-chart {type}` - Create charts
- `/viz-dashboard {template}` - Create layouts

8
plugins/viz-platform/commands/viz-dashboard.md
View File

@@ -2,7 +2,7 @@
description: Create a dashboard layout with the layout-builder agent
---
# Create Dashboard
# Viz Dashboard
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Create a dashboard layout with filters, grids, and sections.
## Usage
```
/dashboard {template}
/viz-dashboard {template}
```
## Arguments
@@ -37,5 +37,5 @@ Activates **layout-builder** agent which orchestrates:
## Related Commands
- `/breakpoints {layout}` - Configure responsive breakpoints
- `/chart {type}` - Add charts to layout
- `/viz-breakpoints {layout}` - Configure responsive breakpoints
- `/viz-chart {type}` - Add charts to layout

6
plugins/viz-platform/commands/viz-setup.md
View File

@@ -2,7 +2,7 @@
description: Interactive setup wizard for viz-platform plugin
---
# Viz-Platform Setup Wizard
# Viz Setup
## Visual Output
@@ -41,5 +41,5 @@ Verify MCP server loads, display summary, prompt session restart.
## Related Commands
- `/component {name}` - Inspect component props
- `/chart {type}` - Create a chart
- `/viz-component {name}` - Inspect component props
- `/viz-chart {type}` - Create a chart

8
plugins/viz-platform/commands/viz-theme-css.md
View File

@@ -2,7 +2,7 @@
description: Export a theme as CSS custom properties
---
# Export Theme as CSS
# Viz Theme CSS
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Export a theme's design tokens as CSS custom properties.
## Usage
```
/theme-css {name}
/viz-theme-css {name}
```
## Arguments
@@ -38,5 +38,5 @@ Use cases: external CSS, design handoff, documentation, other frameworks.
## Related Commands
- `/theme {name}` - Apply a theme
- `/theme-new {name}` - Create a new theme
- `/viz-theme {name}` - Apply a theme
- `/viz-theme-new {name}` - Create a new theme

8
plugins/viz-platform/commands/viz-theme-new.md
View File

@@ -2,7 +2,7 @@
description: Create a new custom theme with design tokens
---
# Create New Theme
# Viz Theme New
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Create a new custom theme with specified design tokens.
## Usage
```
/theme-new {name}
/viz-theme-new {name}
```
## Arguments
@@ -37,5 +37,5 @@ theme_validate(theme_name="corporate")
## Related Commands
- `/theme {name}` - Apply a theme
- `/theme-css {name}` - Export theme as CSS
- `/viz-theme {name}` - Apply a theme
- `/viz-theme-css {name}` - Export theme as CSS

8
plugins/viz-platform/commands/viz-theme.md
View File

@@ -2,7 +2,7 @@
description: Apply an existing theme to the current context
---
# Apply Theme
# Viz Theme
## Skills to Load
- skills/mcp-tools-reference.md
@@ -21,7 +21,7 @@ Apply an existing theme to activate its design tokens.
## Usage
```
/theme {name}
/viz-theme {name}
```
## Arguments
@@ -41,5 +41,5 @@ When activated, new charts/layouts automatically use theme tokens.
## Related Commands
- `/theme-new {name}` - Create a new theme
- `/theme-css {name}` - Export theme as CSS
- `/viz-theme-new {name}` - Create a new theme
- `/viz-theme-css {name}` - Export theme as CSS