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>
47 lines
869 B
Markdown
47 lines
869 B
Markdown
---
|
|
name: viz theme
|
|
description: Apply an existing theme to the current context
|
|
---
|
|
|
|
# /viz theme
|
|
|
|
## Skills to Load
|
|
- skills/mcp-tools-reference.md
|
|
- skills/theming-system.md
|
|
|
|
## Visual Output
|
|
|
|
```
|
|
+------------------------------------------------------------------+
|
|
| VIZ-PLATFORM - Apply Theme |
|
|
+------------------------------------------------------------------+
|
|
```
|
|
|
|
Apply an existing theme to activate its design tokens.
|
|
|
|
## Usage
|
|
|
|
```
|
|
/viz theme {name}
|
|
```
|
|
|
|
## Arguments
|
|
|
|
- `name` (required): Theme name to activate
|
|
|
|
## Tool Mapping
|
|
|
|
```python
|
|
theme_activate(theme_name="dark")
|
|
theme_list() # List available themes
|
|
```
|
|
|
|
## Theme Effects
|
|
|
|
When activated, new charts/layouts automatically use theme tokens.
|
|
|
|
## Related Commands
|
|
|
|
- `/viz theme-new {name}` - Create a new theme
|
|
- `/viz theme-css {name}` - Export theme as CSS
|