domain-driven-design
Installation
SKILL.md
Domain-Driven Design
Review the domain shape of a change through the lenses from Learning Domain-Driven Design (Vlad Khononov, O'Reilly). DDD works at two altitudes that compose:
- Strategic (Parts I, III–IV) — where the boundaries are: bounded contexts, ubiquitous language, and how contexts integrate.
- Tactical (Parts II–III) — how one context is built: the business-logic pattern, and whether aggregates/value-objects hold their invariants and publish events safely.
This is not a generic layering/cohesion check or trade-off/connascence audit (use architecture-lens), not macro style selection or service decomposition (use macro-architecture), and not a bug hunt (use code-review).
Select the review
| Change | Read |
|---|---|
| Moves or crosses a bounded context, changes business naming, or integrates another system | references/strategic-review.md |
| Structures business logic, aggregates, value objects, or domain events inside one context | references/tactical-review.md |
| Does both | Strategic review first, then the affected tactical rules; boundaries constrain the internal design |
Apply only the relevant lenses. Report findings with file and line, the rule, and a proposed fix. A clean lens needs no invented finding.