feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
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>
This commit is contained in:
71
plugins/viz-platform/commands/viz-design-review.md
Normal file
71
plugins/viz-platform/commands/viz-design-review.md
Normal file
@@ -0,0 +1,71 @@
|
||||
---
|
||||
name: viz design-review
|
||||
description: Audit codebase for design system compliance
|
||||
arguments:
|
||||
- name: path
|
||||
description: File or directory to audit
|
||||
required: true
|
||||
---
|
||||
|
||||
# /viz design-review
|
||||
|
||||
Scans target path for Dash Mantine Components usage and validates against design system standards.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/viz design-review <path>
|
||||
```
|
||||
|
||||
**Examples:**
|
||||
```
|
||||
/viz design-review ./app/pages/
|
||||
/viz design-review ./app/components/dashboard.py
|
||||
/viz design-review .
|
||||
```
|
||||
|
||||
## What It Does
|
||||
|
||||
1. **Activates** the `design-reviewer` agent in review mode
|
||||
2. **Loads** the `skills/design-system-audit.md` skill
|
||||
3. **Scans** target path for:
|
||||
- Python files with DMC imports
|
||||
- Component instantiations and their props
|
||||
- Style dictionaries and color values
|
||||
- Accessibility attributes
|
||||
4. **Validates** against:
|
||||
- DMC component registry (valid components and props)
|
||||
- Theme token usage (no hardcoded colors/sizes)
|
||||
- Accessibility standards (contrast, ARIA labels)
|
||||
5. **Produces** detailed report grouped by severity
|
||||
|
||||
## Output
|
||||
|
||||
Generates a comprehensive audit report with:
|
||||
|
||||
- **FAIL**: Invalid props, deprecated components, missing required props
|
||||
- **WARN**: Hardcoded colors/sizes, missing accessibility attributes
|
||||
- **INFO**: Optimization suggestions, consistency recommendations
|
||||
|
||||
Each finding includes:
|
||||
- File path and line number
|
||||
- Description of the issue
|
||||
- Recommended fix
|
||||
|
||||
## When to Use
|
||||
|
||||
- **Before PR review**: Catch design system violations early
|
||||
- **On existing codebases**: Audit for compliance gaps
|
||||
- **During refactoring**: Ensure changes maintain compliance
|
||||
- **Learning**: Understand design system best practices
|
||||
|
||||
## Related Commands
|
||||
|
||||
- `/viz design-gate` - Binary pass/fail for sprint execution (no detailed report)
|
||||
- `/viz component` - Inspect individual DMC component props
|
||||
- `/viz theme` - Check active theme configuration
|
||||
|
||||
## Requirements
|
||||
|
||||
- viz-platform MCP server must be running
|
||||
- Target path must contain Python files with DMC usage
|
||||
Reference in New Issue
Block a user