Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/architecture-paradigm-domain-driven
Models a business in its own language.
Passed 21 of 22 test cases with the skill, and 12 of 22 without it.
and 12 more in the full report
9 fixed12 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before declaring a service architecture compliant with safety standards, what audit step must be completed for all data types that cross system network boundaries?
| Checked | Without skill | With skill |
|---|---|---|
| Requires performing a field audit on every type crossing an IO boundary to verify what data is exposed. | Missed | Passed |
The instructions your model reads when the skill loads.
Design for the future, build for now.
DDD is modeling a business in the business's own language. The goal is not to avoid structure. It is to avoid structure you cannot back out of, and to defer structure you do not yet need.
Ubiquitous language, bounded contexts, and a model built by talking to the people who do the work. The measure of a domain model is whether a person in the business would recognize their own job in it.
Clean Architecture. Mandatory layering. A mapper between every tier. A count of design patterns applied before the first line of business logic is written.
These are DDD-adjacent choices. Each has its own justification, and none of them is entailed by DDD. Wanting to decouple an API from the domain is a good reason to add a DTO. "This is what DDD requires" is not, because it does not.
The building blocks are not the point, and this is not the repo's opinion. Evans said so himself, ten years after the book, about the book:
"things like the entities and value objects [..] [People] come away thinking that that's really the core of DDD, whereas, in fact, it's really not."
"I really think that the way I arranged the book gives people the wrong emphasis, so that's the biggest part of what I do is rearrange those things."
Source: SE-Radio Episode 226, "Eric Evans on Domain-Driven Design at 10 Years" (video). Quotes as
test cases passed, vs 12 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.