Domain Driven Design
Use for domain-driven design, domain modeling, ubiquitous language, bounded contexts, aggregates, invariants, entities, value objects, domain services, domain events, and deciding whether a rich domain model is warranted.
Install
/plugin marketplace add eralmansouri/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add eralmansouri/skills --skill domain-driven-designgit clone --depth 1 https://github.com/eralmansouri/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/domain-driven-design ~/.claude/skills/domain-driven-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Domain-Driven Design Model business behavior before choosing tactical patterns. DDD addresses inherent business complexity: rules, decisions, workflows, language, and ownership. It is not a required folder structure or a checklist of entities, repositories, factories, and events. ## Workflow 1. State the business objective, actors, use cases, constraints, and desired outcome. 2. Model the real workflow collaboratively with domain experts. Capture actions, facts, decisions, failures, handoffs, and pain points. 3. Build context-specific ubiquitous language. Record ambiguous terms and different meanings explicitly. 4. Find boundaries through capabilities, ownership, lifecycle, language shifts, consistency needs, and reasons to change. 5. Classify core, supporting, and generic areas. Spend rich-modeling effort where complexity or competitive value warrants it. 6. For each use case, name the command by intent and identify the business facts it can produce. 7. Enumerate invariants and the state required to enforce each one reliably. 8. Choose the smallest implementation: transaction script, database constraint, policy, value object, or aggregate. 9. Keep read composition separate from write-side consistency decisions. 10. Test allowed and rejected transitions, then revise the model as understanding changes. ## Strategic Model A bounded context owns the meaning, behavior, rules, lifecycle, authority, and
Details
- Skill name
domain-driven-design- Repository
- eralmansouri/skills
- Path
skills/domain-driven-design/SKILL.md- Repo updated
- 15 October 2026
FAQ
What does the Domain Driven Design skill do?
Use for domain-driven design, domain modeling, ubiquitous language, bounded contexts, aggregates, invariants, entities, value objects, domain services, domain events, and deciding whether a rich domain model is warranted.
How do I install the Domain Driven Design skill?
Claude Code plugin: /plugin marketplace add eralmansouri/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Domain Driven Design popular?
It lives in eralmansouri/skills, which has 9 GitHub stars and 2 forks.
Related skills
Codebase Design
9eralmansouri/skills
Use for code-level module design, deep modules, interfaces, seams, adapters, testability, refactoring shallow modules, and finding architecture improvements in an existing codebase.
Design Review
9eralmansouri/skills
Design review of a codebase area, branch, or PR. Maps its bounded contexts, vertical slices, and modules, then judges where rules live and whether flexibility sits where change actually happens. Use when the user asks for a design or architecture review, or when a review should judge structure rather than bugs or style.
Event Driven Systems
9eralmansouri/skills
Use for event-driven or message-driven architecture, commands and events, queues, pub/sub, Kafka, choreography, orchestration, sagas, outbox, idempotency, retries, ordering, backpressure, consumer lag, and messaging operations.
End Game Thinking
5shosmer/end-game-thinking-skill
Strategic foresight methodology for reasoning backward from possible futures to identify defensible positions in the present. Combines backward induction, inversion, premortem analysis, regret minimization, and scenario stress-testing into a structured exercise that produces a written artifact. MANDATORY TRIGGERS: end game thinking, endgame, what positions should I hold, how do I prepare for AI, future-proofing, strategic positioning, what happens when AI, stress test my strategy, what are my blindspots, competitive positioning for AI, scenario planning, backward induction, inversion exercise,
Coti Starter Grant
9coti-io/coti-skills
Requests and claims a one-time starter COTI token grant for new agents. Use when user asks to 'get starter COTI', 'claim starter grant', 'onboard agent', 'get free COTI', or 'fund my new wallet'. Handles the challenge-response flow for initial token funding.
Improve Agent
9duvoai/skills
Run the guided, end-to-end loop that makes one Duvo Agent better. Use when the user wants to "improve this Agent", "make my Agent better", "help me tune this Agent", "this Agent isn't good enough", "fix this Agent based on its Runs", or asks you to take an Agent from where it is to a concrete, applied improvement — not just a read-only audit. You drive the conversation: pin the Agent, survey its whole setup (AOP, Connections, Skills, triggers, memory, recent Runs), agree on what to base the improvement on (the user's feedback or the evidence in the Runs), propose a Run range and confirm it, ge
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.