Domain driven design
Skill kimtth/agent-skill-100-lines-or-less/skills/domain-driven-design
Use when: model a complex domain with a shared language, bounded contexts, and clear aggregates.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill domain-driven-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 188 tokens by cl100k_base, as published. Nobody here has run it
Goal: software whose structure mirrors the business domain.
Use for:
- complex domains with rich rules and vocabulary
- untangling a tangled model into clear boundaries
- aligning code with how the business actually speaks
Workflow:
- Build a ubiquitous language with domain experts.
- Identify bounded contexts and their boundaries.
- Model aggregates that enforce invariants as a unit.
- Separate entities (identity) from value objects (equality by value).
- Keep domain logic in the model, not in services or controllers.
- Map context relationships explicitly.
Building blocks:
- entities, value objects, and aggregates
- domain events for cross-aggregate effects
- repositories for aggregate persistence
- anti-corruption layers between contexts
Rules:
- one ubiquitous language per bounded context
- aggregates protect their own invariants
- do not leak domain logic into infrastructure
- keep contexts decoupled; translate at the edges
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.