Domain Driven Design
Apply Domain-Driven Design (DDD) by Eric Evans and Vaughn Vernon when modeling complex business domains, designing aggregates, structuring bounded contexts, choosing between entities and value objects, or aligning code with domain language. Covers strategic design (ubiquitous language, bounded contexts, context mapping), tactical building blocks (entities, value objects, aggregates, domain events, services, repositories, factories), supple design, and refactoring toward deeper insight.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill domain-driven-designgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/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 (Eric Evans) Apply DDD when modeling complex business domains, designing system boundaries, deciding what is an entity vs a value object, structuring aggregates, or aligning code with the language of domain experts. DDD is about *tackling complexity in the heart of software* — when the domain is simple, simpler approaches are better. ## Core Philosophy **The model is the heart of the software.** Code, conversations, and diagrams should all express the same model. When they diverge, the model is failing. **Software complexity comes from the domain, not the technology.** The hardest problem is understanding what the business actually does and encoding it faithfully. **Knowledge crunching is continuous.** Designers, developers, and domain experts iterate on a shared model. Insights emerge over time; the model evolves. **Embrace breakthroughs.** Periodically, accumulated learning reveals a much better model. Refactor toward it rather than patch the old one. --- ## Strategic Design Strategic design addresses the structure of the system as a whole — how large systems are partitioned and how parts relate. ### Ubiquitous Language A shared, rigorous language used by developers and domain experts alike, in conversation, documentation, AND code. - Class names, method names, and event names come straight from this language. - If a domain expert says "Shipment", code says `Shipment` — not `Parcel`, not `Package`, not `Order`.
Details
- Skill name
domain-driven-design- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/domain-driven-design/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Domain Driven Design skill do?
Apply Domain-Driven Design (DDD) by Eric Evans and Vaughn Vernon when modeling complex business domains, designing aggregates, structuring bounded contexts, choosing between entities and value objects, or aligning code with domain language. Covers strategic design (ubiquitous language, bounded contexts, context mapping), tactical building blocks (entities, value objects, aggregates, domain events, services, repositories, factories), supple design, and refactoring toward deeper insight.
How do I install the Domain Driven Design skill?
Claude Code plugin: /plugin marketplace add vnovakovits/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 vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Event Storming
5vnovakovits/claude-skills
Apply Alberto Brandolini's Event Storming — a collaborative modeling technique using domain events on sticky notes to discover business processes, identify bounded contexts, and design software collaboratively. Covers Big Picture, Process Modeling, and Software Design levels, the color-coded sticky-note grammar, the workshop flow, and how Event Storming pairs with DDD. Use when starting a new project, exploring a complex domain, finding bounded-context seams, designing aggregates, or surfacing hidden assumptions across business and tech.
Dify Tool Developer
8Freddy-CHEN-ux/00_claude_skills
Guide AI agents through Dify tool plugin development with mandatory documentation loading and direct CLI usage. Use when creating Dify tool plugins or extending Dify with custom tools.
Flow Efficiency
5vnovakovits/claude-skills
Apply Niklas Modig & Pär Åhlström's flow-efficiency framework from "This is Lean — Resolving the Efficiency Paradox" (2012). Covers the central paradox (resource efficiency vs flow efficiency), the efficiency matrix, Kingman's formula and why high utilization destroys flow, the three laws of process dynamics (Little's Law, the law of bottlenecks, the law of variation), the "variation × utilization" killer combination, lean as an operational strategy not a tool, and the diagnostic vocabulary for explaining why "keeping everyone busy" actively harms delivery. Use when a team is busy but not ship
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.