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>
2.3 KiB
2.3 KiB
name, description, gate_contract, arguments
| name | description | gate_contract | arguments | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| viz design-gate | Design system compliance gate (pass/fail) for sprint execution | v1 |
|
/viz design-gate
Binary pass/fail validation for design system compliance. Used by projman orchestrator during sprint execution to gate issue completion.
Usage
/viz design-gate <path>
Examples:
/viz design-gate ./app/pages/dashboard.py
/viz design-gate ./app/components/
What It Does
- Activates the
design-revieweragent in gate mode - Loads the
skills/design-system-audit.mdskill - Scans target path for DMC usage
- Checks only for FAIL-level violations:
- Invalid component props
- Non-existent components
- Missing required props
- Deprecated components
- Returns binary result:
PASS- No blocking violations foundFAIL- One or more blocking violations
Output
On PASS
DESIGN GATE: PASS
No blocking design system violations found.
On FAIL
DESIGN GATE: FAIL
Blocking Issues (2):
1. app/pages/home.py:45 - Invalid prop 'onclick' on dmc.Button
Fix: Use 'n_clicks' for click handling
2. app/components/nav.py:12 - Component 'dmc.Navbar' not found
Fix: Use 'dmc.AppShell.Navbar' (DMC v0.14+)
Run /viz design-review for full audit report.
Integration with projman
This command is automatically invoked by the projman orchestrator when:
- An issue has the
Domain/Vizlabel - The orchestrator is about to mark the issue as complete
- The orchestrator passes the path of changed files
Gate behavior:
- PASS -> Issue can be marked complete
- FAIL -> Issue stays open, blocker comment added
Differences from /viz design-review
| Aspect | /viz design-gate | /viz design-review |
|---|---|---|
| Output | Binary PASS/FAIL | Detailed report |
| Severity | FAIL only | FAIL + WARN + INFO |
| Purpose | Automation gate | Human review |
| Verbosity | Minimal | Comprehensive |
When to Use
- Automated pipelines: CI/CD design system checks
- Sprint execution: Automatic quality gates
- Quick validation: Fast pass/fail without full report
For detailed findings, use /viz design-review instead.
Requirements
- viz-platform MCP server must be running
- Target path must exist