1.7 KiB
1.7 KiB
allowed-tools, description, wave-enabled, complexity-threshold
| allowed-tools | description | wave-enabled | complexity-threshold | |||||
|---|---|---|---|---|---|---|---|---|
|
Design system architecture, APIs, and component interfaces | true | 0.6 |
/hc:design - System and Component Design
Purpose
Design system architecture, APIs, component interfaces, and technical specifications.
Usage
/hc:design [target] [--type architecture|api|component|database] [--format diagram|spec|code]
Arguments
target- System, component, or feature to design--type- Design type (architecture, api, component, database)--format- Output format (diagram, spec, code)--iterative- Enable iterative design refinement
Execution
- Use @agent-architect to analyze requirements and design constraints
- PARALLEL: Engage @agent-designer for visual components while @agent-architect works on system design
- @agent-architect creates system design and architectural patterns (parallel with step 4)
- @agent-designer creates UI specifications and component designs (parallel with step 3)
- Pass design specs to @agent-coder for implementation planning
- Validate design against requirements and best practices
- Generate design documentation and implementation guides
Note: Steps 2-4 execute in parallel for optimal performance per CLAUDE.md directives
Claude Code Integration
- Uses Task tool to orchestrate @agent-architect and @agent-designer in parallel
- Uses Read for requirement analysis
- Uses Task for design documentation and specification creation
- Applies TodoWrite for design task tracking
- Maintains consistency with architectural patterns
- Shares design specifications between agents via MCP memory server