mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
d24503ca02
- Migrate all command files to use @include reference system - Consolidate shared patterns into new yml structure - Create central superclaude shared configuration files - Remove deprecated markdown files (MCP.md, PERSONAS.md, RULES.md) - Add new documentation structure in docs/ - Update installation script for new architecture - Add ROADMAP.md and VERSION files This completes the major architectural refactor to improve maintainability and reduce duplication across the SuperClaude command system. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
53 lines
2.0 KiB
Markdown
53 lines
2.0 KiB
Markdown
**Purpose**: System architecture and API design
|
|
|
|
---
|
|
|
|
@include shared/universal-constants.yml#Universal_Legend
|
|
|
|
## Command Execution
|
|
Execute: immediate. --plan→show plan first
|
|
Legend: Generated based on symbols used in command
|
|
Purpose: "[Action][Subject] in $ARGUMENTS"
|
|
|
|
Design system architecture & APIs for $ARGUMENTS.
|
|
|
|
@include shared/flag-inheritance.yml#Universal_Always
|
|
|
|
Examples:
|
|
- `/design --api --think` - REST API design w/ patterns
|
|
- `/design --ddd --think-hard` - Deep domain modeling
|
|
- `/design --api --ddd --ultrathink` - Complete system architecture
|
|
|
|
Design modes:
|
|
|
|
**--api:** Design REST or GraphQL APIs
|
|
- w/ --openapi: Generate OpenAPI 3.0 spec | w/ --graphql: Create GraphQL schema & resolvers
|
|
- Include auth, rate limiting & error handling | Design→scalability & maintainability
|
|
|
|
**--ddd:** Apply DDD principles
|
|
- w/ --bounded-context: Define context boundaries & mappings
|
|
- Design entities, value objects & aggregates | Create domain services & events | Impl repository patterns
|
|
|
|
**--prd:** Create PRD
|
|
- w/ --template: Use template (feature/api/integration/migration)
|
|
- Include user stories w/ acceptance criteria | Define success metrics & timelines | Document tech requirements
|
|
|
|
## Design Patterns
|
|
|
|
@include shared/architecture-patterns.yml#API_Design_Patterns
|
|
|
|
@include shared/architecture-patterns.yml#DDD_Patterns
|
|
|
|
@include shared/architecture-patterns.yml#PRD_Templates
|
|
|
|
## Integration & Best Practices
|
|
|
|
Combined modes: API+DDD: Design domain-driven APIs | API+PRD: Create API product requirements | DDD+PRD: Document domain-driven architecture | All three: Complete system design
|
|
|
|
Best practices: Start w/ user needs & business goals | Design→change & evolution | Consider non-functional early | Document decisions & rationale | Include examples & diagrams | Plan→testing & monitoring
|
|
|
|
@include shared/research-patterns.yml#Mandatory_Research_Flows
|
|
|
|
@include shared/docs-patterns.yml#Standard_Notifications
|
|
|
|
@include shared/universal-constants.yml#Standard_Messages_Templates |