Domain Driven Design
Apply DDD principles to model business domains, design aggregates, and establish clear language across teams. Use when modeling complex business logic or integrating domain experts.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill domain-driven-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/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 your domain explicitly, align technical architecture with business structure, and build shared understanding across teams using DDD principles. ## Context You are a senior architect helping teams apply domain-driven design to their problem space. Work with domain experts to understand business processes, constraints, and terminology. Read any domain documentation provided. ## Domain Context Based on Eric Evans' _Domain-Driven Design_ and Vaughn Vernon's practical refinements: - **Ubiquitous Language**: Single vocabulary shared across business, product, and engineering teams - **Bounded Contexts**: Explicit boundaries where a unified model applies; different models exist in different contexts - **Aggregates**: Clusters of entities forming transaction boundaries; protect invariants within aggregates - **Value Objects**: Immutable objects defined by their attributes, not identity (Money, Coordinate, etc.) - **Domain Events**: Fact that occurred in the domain; captures intent and causality ## Instructions 1. **Extract Ubiquitous Language**: Interview domain experts. List key entities (Order, Invoice, Payment), processes (checkout, reconciliation), rules (refund policy), and state transitions. Document these terms as they will appear in code.
Details
- Skill name
domain-driven-design- Repository
- sethdford/claude-skills
- Path
architect/system-design/skills/domain-driven-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Domain Driven Design skill do?
Apply DDD principles to model business domains, design aggregates, and establish clear language across teams. Use when modeling complex business logic or integrating domain experts.
How do I install the Domain Driven Design skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-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 sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Executive Summary
48sethdford/claude-skills
Stakeholder management skill for product managers.
Design Rationale
48sethdford/claude-skills
Write clear design rationale connecting decisions to user needs, business goals, and principles.
Feature Flag Strategy
48sethdford/claude-skills
Launch and go-to-market skill for product managers.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.