ddd-playbook
Guides DDD discovery for the ToDo domain: ubiquitous language, bounded context, aggregates, invariants.
When & Why to Use This Skill
The DDD Playbook is a specialized Claude skill designed to guide developers and architects through the Domain-Driven Design (DDD) discovery process. It provides a structured framework for defining ubiquitous language, establishing bounded contexts, and modeling aggregates and invariants specifically for the ToDo domain, ensuring a robust and maintainable software architecture.
Use Cases
- Domain Modeling: Systematically defining business entities, aggregates, and invariants to create a clean and scalable system design for task management applications.
- Ubiquitous Language Development: Building and maintaining a project-specific glossary to align technical implementation with business requirements and terminology.
- Architectural Training: Serving as a guided exercise for developers to learn and apply DDD principles in a controlled, practical environment using the ToDo domain as a reference.
| name | ddd-playbook |
|---|---|
| description | Guides DDD discovery for the ToDo domain: ubiquitous language, bounded context, aggregates, invariants. |
| allowed-tools | Read, Grep, Glob, Edit, Write |
DDD Playbook (ToDo training)
- Update glossary first.
- Keep one bounded context: "Todo Management".
- Propose a minimal aggregate and max 5 invariants at a time.
- For each capability, update model + invariants + use-case contract. Never introduce advanced patterns unless asked.