Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
name, description
| name | description |
|---|---|
| viz setup | Interactive setup wizard for viz-platform plugin |
/viz setup
Visual Output
+------------------------------------------------------------------+
| VIZ-PLATFORM - Setup Wizard |
+------------------------------------------------------------------+
Sets up viz-platform with DMC validation and theming.
Note: Uses Bash/Read/Write tools - NOT MCP tools. Restart session after setup.
Phase 1: Environment Validation
Check Python 3.10+ and DMC installation:
python3 --version
python3 -c "import dash_mantine_components as dmc; print(dmc.__version__)"
Phase 2: MCP Server Setup
Locate and create venv if missing:
cd /path/to/mcp-servers/viz-platform && python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
Phase 3: Theme Preferences (Optional)
Ask user about color scheme and primary color. Save to ~/.config/claude/viz-platform.env.
Phase 4: Validation
Verify MCP server loads, display summary, prompt session restart.
Related Commands
/viz component {name}- Inspect component props/viz chart {type}- Create a chart