domain-driven-design

by ciembor3.0k

Apply Eric Evans-inspired DDD rules when modeling a complex domain, defining bounded contexts, protecting ubiquitous language, or designing aggregates.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add ciembor/agent-rules-books --skill domain-driven-design -a cursor -y

Download skill domain-driven-design/SKILL.md on GitHub

Related skills

View all

A
a-philosophy-of-software-designApply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.
C
clean-architectureApply Robert C. Martin-inspired architecture rules when separating business policy from frameworks, databases, UI, or infrastructure details.
C
clean-codeApply Robert C. Martin-inspired clean code rules when improving readability, naming, function design, responsibilities, or testable everyday code.

Questions

How do I install domain-driven-design?: Download domain-driven-design/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does domain-driven-design live?: The publisher keeps it at https://github.com/ciembor/agent-rules-books.
Which agents can use domain-driven-design?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: domain-driven-design description: Apply Eric Evans-inspired DDD rules when modeling a complex domain, defining bounded contexts, protecting ubiquitous language, or designing aggregates. license: MIT

Domain-Driven Design Skill

Use this skill when a task involves strategic domain modeling, ubiquitous language, bounded contexts, context mapping, aggregates, repositories, domain services, or model-driven design.

Before making design or code decisions, read and apply domain-driven-design.mini.md. Use domain-driven-design.md only as a deeper reference when the mini rules are not enough for the current domain-modeling tradeoff.