lmiranda
2d51df7a42
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>
822 B
822 B
name, description
| name | description |
|---|---|
| viz theme-css | Export a theme as CSS custom properties |
/viz theme-css
Skills to Load
- skills/mcp-tools-reference.md
- skills/theming-system.md
Visual Output
+------------------------------------------------------------------+
| VIZ-PLATFORM - Theme CSS Export |
+------------------------------------------------------------------+
Export a theme's design tokens as CSS custom properties.
Usage
/viz theme-css {name}
Arguments
name(required): Theme name to export
Tool Mapping
theme_export_css(theme_name="corporate")
Use cases: external CSS, design handoff, documentation, other frameworks.
Related Commands
/viz theme {name}- Apply a theme/viz theme-new {name}- Create a new theme