Architecture Domain Driven Design
Use when the user asks about DDD, domain-driven design, bounded contexts, aggregates and aggregate roots, ubiquitous language, context maps, anti-corruption layers, event storming or value objects. Produces strategic and tactical domain models. Not for simple CRUD apps or folder layering (use backend-clean-architecture) or service decomposition (use microservices).
Install
npx skills add j4flmao/agent-skills --skill architecture-domain-driven-designgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/architecture/system-design/domain-driven-design ~/.claude/skills/architecture-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
## Purpose
DDD aligns software structure with the business: a shared language inside explicit boundaries, models that enforce business invariants, and deliberate translation where contexts meet. Use it where domain complexity is the main risk (pricing, underwriting, logistics, billing). For simple CRUD, plain layered code is cheaper.
## Agent Protocol
### Trigger
"DDD", "bounded context", "aggregate", "aggregate root", "entity vs value object", "domain event", "context map", "anti-corruption layer", "ubiquitous language", "event storming".
### Input Context
- Business capabilities and processes; domain experts' vocabulary.
- Current pain: tangled models, inconsistent rules, overloaded terms.
- Team structure (contexts usually map to team ownership).
- Persistence and integration constraints.
### Output Artifact
Strategic map (subdomains, contexts, relationships) and/or tactical model (aggregates with invariants, value objects, events, repository interfaces).
### Response Format
```
Subdomains: {core|supporting|generic}: {name}
Contexts: {name} owns {terms}; team {x}
Context map: {upstream} -> {downstream} [{pattern}]
Aggregate: {Root} invariants: {list}; references others by id
Events: {PastTenseName}(fields)
```
### Completion Criteria
- [ ] Each term defined per context (no global "User"/"Product" model).
- [ ] Every aggregate lists the invariants it protects.
- [ ] One aggregate modified per transaction; others updated via events.Details
- Skill name
architecture-domain-driven-design- Repository
- j4flmao/agent-skills
- Path
skills/architecture/system-design/domain-driven-design/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Architecture Domain Driven Design skill do?
Use when the user asks about DDD, domain-driven design, bounded contexts, aggregates and aggregate roots, ubiquitous language, context maps, anti-corruption layers, event storming or value objects. Produces strategic and tactical domain models. Not for simple CRUD apps or folder layering (use backend-clean-architecture) or service decomposition (use microservices).
How do I install the Architecture Domain Driven Design skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill architecture-domain-driven-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Architecture Domain Driven Design popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Architecture Postgresql Internals
45j4flmao/agent-skills
Use when the user asks about Postgres MVCC, the write-ahead log (WAL), table bloat, autovacuum, dead tuples, transaction ID wraparound, checkpoints, HOT updates, EXPLAIN ANALYZE or why Postgres is slow. Produces diagnosis queries and tuning settings. Not for schema design (use data-relational-database) or sharding (use architecture-database-scaling).
Architecture Crdts
45j4flmao/agent-skills
Use when the user asks about CRDTs, real-time collaborative editing, Yjs, Automerge, Loro, local-first apps, offline sync with automatic merge or OT vs CRDT. Produces CRDT type and library choice, sync and persistence architecture. Not for consensus-based consistency (use distributed-consensus) or offline caching without concurrent edits (use mobile-offline-first).
Authoritative Server
45j4flmao/agent-skills
Use when the user asks about an authoritative game server, dedicated server, server tick loop, snapshots, input authority, server reconciliation, rollback or lag compensation on the server. Produces tick loop and world-state design. Not for client-side prediction (use multiplayer-netcode) or fleet scaling (use scaling-architecture).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.