Files
SuperClaude/.claude/commands/design.md
NomenAK 23a103d5dc refactor: Standardize @include reference system across all command files
- Fix @include references to use underscore format (Universal_Legend, Standard_Messages_Templates)
- Add missing ultracompressed.yml shared pattern file
- Update broken reference paths in all 18 command files
- Ensure consistent template naming across command system
- Optimize command file structure with standardized includes

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-06-25 00:21:27 +02:00

1.9 KiB

@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