← ClaudeAtlas

dddlisted

Applies Domain-Driven Design: subdomain classification, context mapping, legacy integration (ACL), tactical pattern choice, and conventions for aggregates, value objects, events, and event sourcing. Use for DDD design or review.
fabiandistler/agents · ★ 2 · Web & Frontend · score 62
Install: claude install-skill fabiandistler/agents
# DDD Strategic design decides *where* to invest; tactical design decides *how* to build. Match the investment to the value — over-engineering a Supporting subdomain and under-investing a Core one are both failures of the same discipline. ## When to use Whenever a design conversation touches subdomain classification, buy-vs-build for a capability, integration with a legacy or third-party system, bounded-context boundaries, or how much domain modeling a piece of business logic actually deserves — *and* whenever implementing domain logic, persisting aggregates, publishing events, or wiring cross-context integration — even if the user never says "DDD". Use the decision path below for the upfront design choice, the workflow for the design conversation, and the reference files as the code-review checklist while writing. ## Core principle A subdomain's strategic classification (Core / Generic / Supporting) should drive both *how much* engineering effort it gets and *which tactical pattern* implements it. Never let architectural enthusiasm outrun the subdomain's actual importance. ## Decision path Walk questions 1–4 in order and stop at the first "yes"; question 5 is a follow-up, not a further rung: 1. **Does the subdomain involve monetary transactions, regulatory audit requirements, or a genuine need for full history / deep analytics / point-in-time reconstruction?** → **Event-Sourced Domain Model.** Read `references/event-sourcing.md` when this fires. 2. **Does the subdoma