domain-driven-design

domain-driven-design is a skill for Claude Code, Codex from joaquimscosta/arkhe-claude-plugins. It costs 124 tokens per session (1,049 once invoked), scanned A, original, MIT.

A guide to Domain-Driven Design, or DDD—a way to shape software around a business’s rules, language, and boundaries. It covers business areas, bounded contexts, aggregates, entities, value objects, and architecture choices.

In plain words
What is it for?
Use it to discover business domains, define boundaries between them, map their relationships, choose a modular monolith or services, and design domain models.
Why use it?
It helps manage systems with complicated business rules by separating concepts that should not be mixed together. It also explains when DDD is unnecessary for simple applications.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to discover business domains, define boundaries between them, map their relationships, choose a modular monolith or services, and design domain models.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add joaquimscosta/arkhe-claude-plugins --skill domain-driven-design
Clone the repo
git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-plugins

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for domain-driven-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design/github.svg)](https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design)
Your own site
<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for domain-driven-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/domain-driven-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,049 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00124 $0.01049
Opus 5.5 $0.00050 $0.00420
Sonnet 5.5 $0.00025 $0.00210
Haiku 4.5 $0.00012 $0.00105

Measured yesterday against content hash c27874c59d86, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

domain-driven-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/spring-boot/skills/domain-driven-design/SKILL.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Domain-Driven Design Skill

DDD manages complexity through alignment between software and business reality. Strategic design (boundaries, language, subdomains) provides more value than tactical patterns (aggregates, repositories).

When to Apply DDD

Apply DDD when:

  • Domain has intricate business rules
  • System is long-lived and high-value
  • Domain experts are available
  • Multiple teams/departments involved
  • Software represents competitive advantage

DDD is overkill when:

  • Simple CRUD applications
  • Tight deadlines, limited budgets
  • No domain experts available
  • Complexity is purely technical, not business

Core Workflow

  1. Domain Discovery → 2. Bounded Context Definition → 3. Context Mapping → 4. Architecture Selection → 5. Tactical Implementation

See WORKFLOW.md for detailed step-by-step instructions for each phase.

Quick Reference

Subdomain Types (Problem Space)

Type Investment Example
Core Maximum - competitive advantage Recommendation engine, trading logic
Supporting Custom but quality tradeoffs OK Inventory management
Generic Buy/outsource Auth, email, payments

Key Decision: Entity vs Value Object

  • Entity: Has identity, tracked through time, mutable → Customer, Order
  • Value Object: Defined by attributes, immutable, interchangeable → Money, Address, Email

Default to value objects. Only use entities when identity matters.

Aggregate Design Rules (Vaughn Vernon)

  1. Model true invariants in consistency boundaries
  2. Design small aggregates (~70% should be root + value objects only)
  3. Reference other aggregates by ID only
  4. Use eventual consistency outside the boundary

Architecture Decision

Start with modular monolith when:
├── Team < 20 developers
├── Domain boundaries unclear
├── Time-to-market critical
└── Strong consistency required

Consider microservices when:
├── Bounded contexts have distinct languages
├── Teams can own full contexts
├── Independent scaling required
└── DevOps maturity exists

Read the full file on GitHub · 99 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 99 lines · 124 tokens per session scan A c27874c59d86

Subscribe to this mod's changes

domain-driven-design is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 124 tokens to every session and 1,049 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-16.