Menu
Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when designing, reviewing, or modifying backend API endpoints, schemas, validation, and API documentation.
Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules.
Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation.
Use when React components are too large or complex and need extraction, simplification, or separation of concerns.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementing or reviewing football data logic, pitch coordinates, event modeling, or sports vision pipelines.
| name | domain-driven-design |
| description | Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code. |
This skill is based on the Domain-Driven Design Crew and industry-standard architectural patterns. Use this to ensure the codebase remains a faithful representation of the business domain.
ResearchBlueprint, don't call it ProjectDraft.Order is the root for OrderItem).id). Its identity persists even if attributes change (e.g., User).Money, Address).InnovationDebateService).interfaces/)application/)domain/)infrastructure/)