mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
ab8904bc8c
Restored 26 additional commands from commitd4a17fc, bringing total from 5 to 30 commands. ## New Commands Added (26): - /analyze - Code and architecture analysis - /brainstorm - Structured brainstorming sessions - /build - Build and compilation workflows - /business-panel - Multi-expert business analysis - /cleanup - Code cleanup and refactoring - /design - System design and architecture - /document - Documentation generation - /estimate - Effort and time estimation - /explain - Code explanation - /git - Git operations and workflows - /help - Command help and usage - /implement - Implementation workflows - /improve - Code improvement suggestions - /index - Project indexing (alias for index-repo) - /load - Load saved sessions - /pm - Project management workflows - /reflect - Reflection and retrospectives - /save - Save current session - /select-tool - Tool selection guidance - /spawn - Spawn parallel tasks - /spec-panel - Multi-expert specification analysis - /task - Task management - /test - Testing workflows - /troubleshoot - Debugging and troubleshooting - /workflow - Custom workflow automation ## Documentation Updates: - Created docs/reference/commands-list.md with categorized command reference - Updated README.md with expandable 30-command list - Updated README-zh.md with Chinese translations - Updated README-ja.md with Japanese translations - Updated README-kr.md with Korean translations - Changed statistics: "3 plugins" → "30 commands" - Added command categories: Planning & Design, Development, Testing & Quality, Documentation, Version Control, Project Management, Research & Analysis, Utilities ## Files Changed: - 60 files changed, 7930 insertions(+), 267 deletions(-) - Added 26 commands to plugins/superclaude/commands/ - Added 26 commands to src/superclaude/commands/ - Created comprehensive command documentation Commands restored from:d4a17fc(superclaude/commands/) Total: 30 commands now available 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
88 lines
3.2 KiB
Markdown
88 lines
3.2 KiB
Markdown
---
|
|
name: design
|
|
description: "Design system architecture, APIs, and component interfaces with comprehensive specifications"
|
|
category: utility
|
|
complexity: basic
|
|
mcp-servers: []
|
|
personas: []
|
|
---
|
|
|
|
# /sc:design - System and Component Design
|
|
|
|
## Triggers
|
|
- Architecture planning and system design requests
|
|
- API specification and interface design needs
|
|
- Component design and technical specification requirements
|
|
- Database schema and data model design requests
|
|
|
|
## Usage
|
|
```
|
|
/sc:design [target] [--type architecture|api|component|database] [--format diagram|spec|code]
|
|
```
|
|
|
|
## Behavioral Flow
|
|
1. **Analyze**: Examine target requirements and existing system context
|
|
2. **Plan**: Define design approach and structure based on type and format
|
|
3. **Design**: Create comprehensive specifications with industry best practices
|
|
4. **Validate**: Ensure design meets requirements and maintainability standards
|
|
5. **Document**: Generate clear design documentation with diagrams and specifications
|
|
|
|
Key behaviors:
|
|
- Requirements-driven design approach with scalability considerations
|
|
- Industry best practices integration for maintainable solutions
|
|
- Multi-format output (diagrams, specifications, code) based on needs
|
|
- Validation against existing system architecture and constraints
|
|
|
|
## Tool Coordination
|
|
- **Read**: Requirements analysis and existing system examination
|
|
- **Grep/Glob**: Pattern analysis and system structure investigation
|
|
- **Write**: Design documentation and specification generation
|
|
- **Bash**: External design tool integration when needed
|
|
|
|
## Key Patterns
|
|
- **Architecture Design**: Requirements → system structure → scalability planning
|
|
- **API Design**: Interface specification → RESTful/GraphQL patterns → documentation
|
|
- **Component Design**: Functional requirements → interface design → implementation guidance
|
|
- **Database Design**: Data requirements → schema design → relationship modeling
|
|
|
|
## Examples
|
|
|
|
### System Architecture Design
|
|
```
|
|
/sc:design user-management-system --type architecture --format diagram
|
|
# Creates comprehensive system architecture with component relationships
|
|
# Includes scalability considerations and best practices
|
|
```
|
|
|
|
### API Specification Design
|
|
```
|
|
/sc:design payment-api --type api --format spec
|
|
# Generates detailed API specification with endpoints and data models
|
|
# Follows RESTful design principles and industry standards
|
|
```
|
|
|
|
### Component Interface Design
|
|
```
|
|
/sc:design notification-service --type component --format code
|
|
# Designs component interfaces with clear contracts and dependencies
|
|
# Provides implementation guidance and integration patterns
|
|
```
|
|
|
|
### Database Schema Design
|
|
```
|
|
/sc:design e-commerce-db --type database --format diagram
|
|
# Creates database schema with entity relationships and constraints
|
|
# Includes normalization and performance considerations
|
|
```
|
|
|
|
## Boundaries
|
|
|
|
**Will:**
|
|
- Create comprehensive design specifications with industry best practices
|
|
- Generate multiple format outputs (diagrams, specs, code) based on requirements
|
|
- Validate designs against maintainability and scalability standards
|
|
|
|
**Will Not:**
|
|
- Generate actual implementation code (use /sc:implement for implementation)
|
|
- Modify existing system architecture without explicit design approval
|
|
- Create designs that violate established architectural constraints |