tactical-ddd — Claude Code skill: what it does, how to install
Audits domain models for anemia and refactors them into rich aggregates using tactical DDD patterns in Claude Code.
MIT ★ 7,191 updated 2026-10-24
npx skills add tech-leads-club/agent-skills --skill tactical-ddd -a claude-codeWhat tactical-ddd does
The skill inspects domain code across three distinct phases. First, it detects signs of anemia, such as setter chains and service methods that mutate external state. Next, it classifies each affected class into an Entity, Value Object, Aggregate, or Domain Service.
When asked to refactor, the skill replaces naked setters with expressive domain methods and pulls logic from services into aggregates. It adds business guards and emits domain events on successful state changes. The agent presents findings first and asks before changing any file.
This tool stops strictly at the domain boundary. It will not decompose microservices or build strategic context maps, and it deliberately ignores DTOs, controllers, and infrastructure adapters.
What it helps with
- Spot anemic domain models and public setter chains in domain logic
- Move business logic from domain services into owning aggregates
- Replace primitive data fields with dedicated Value Objects
- Emit domain events after valid entity state transitions
Example prompts for the agent
- Check the
Orderclass for domain model anemia - Refactor our cart entity to follow tactical DDD patterns
- Review this aggregate and suggest how to protect its invariants
How to install tactical-ddd
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill tactical-ddd -a claude-code2Manually: put the files in place
~/.claude/skills/tactical-ddd/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tactical-ddd/
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill tactical-ddd -a codex2Manually: put the files in place
.agents/skills/tactical-ddd/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill tactical-ddd -a cursor2Manually: put the files in place
.cursor/skills/tactical-ddd/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tech-leads-club/agent-skills 'packages/skills-catalog/skills/(architecture)/tactical-ddd'2Manually: put the files in place
.github/skills/tactical-ddd/SKILL.md1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill tactical-ddd -a gemini-cli2Platform CLI
gemini skills install https://github.com/tech-leads-club/agent-skills --path 'packages/skills-catalog/skills/(architecture)/tactical-ddd'Manually: put the files in place
.devin/skills/tactical-ddd/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tactical-ddd
How to install tactical-ddd in Claude Code?
Run the command npx skills add tech-leads-club/agent-skills --skill tactical-ddd -a claude-code.
What does tactical-ddd do?
It scans domain code for anemia signals, classifies components into tactical DDD building blocks, and rewrites data bags into encapsulated models with business methods.
What code is outside the scope of this skill?
It does not handle strategic DDD context mapping, service boundary decomposition, or layers outside the domain such as DTOs, HTTP controllers, and persistence adapters.
Source text
SKILL.md · MIT
--- name: tactical-ddd description: Detects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Services, Domain Events). Use when the user asks to validate, review, or check domain models or DDD code; detect anemia; refactor domain objects; improve encapsulation; or mentions terms like "anemic model", "rich domain", "aggregate", "value object", "domain event", "ubiquitous language", "is this good DDD", "does this follow DDD", or "check my domain". Do NOT use for module or service boundary design, architectural decomposition, strategic DDD context mapping, or code outside the domain layer (DTOs, controllers, infrastructure adapters). --- # Tactical DDD — Rich Domain Modeling ## Workflow Determine the user's intent first: | Intent | Phases to run | |--------|--------------| | "validate / review / check / is this correct?" | Phase 1 + 2 only → report findings, ask before refactoring | | "fix / refactor / improve / clean up" | Phase 1 + 2 + 3 | | "how should I design / model this?" | Load [reference.md](reference.md) directly | ### Phase 1 — Detect Load [detection.md](detection.md) and scan the target code for anemia signals. Produce a severity score and list of affected classes. ### Phase 2 — Assess For each affected class, determine the correct building block: | Has unique identity tracked over time? | Has invariants tying multiple objects? | → Building Block | |----------------------------------------|----------------------------------------|-----------------| | Yes | — | **Entity** | | No | — | **Value Object** | | Yes (root) + children with shared invariants | Yes | **Aggregate** | | Operation spans multiple Aggregates/doesn't belong to any | — | **Domain Service** | Prefer Value Objects over Entities. Prefer small Aggregates over large ones. **If intent was validate/review**: stop here. Report findings using the output format below. Ask "Would you like me to apply these fixes?" before proceeding. ### Phase 3 — Refactor Load [refactoring.md](refactoring.md) for step-by-step moves. Apply in this order: 1. Replace setter chains with a single expressive method 2. Move service logic into the Aggregate that owns it 3. Add business guards at the top of each method 4. Publish a Domain Event after each successful state change 5. Replace primitive types with Value Objects For deep pattern questions (boundary design, event modeling, service vs. entity decision), load [reference.md](reference.md). --- ## Quick Anemia Signals (scan first) ``` public setX() / public setY() → behaviour should be encapsulated service.doX(entity, ...) → logic likely belongs in entity entity.setA(); entity.setB(); ... → setter chain = missing intent method no domain methods beyond getters → pure data bag ``` --- ## Golden Rules 1. **Behaviour with data** — Objects own both state and the operations that change it 2. **Ubiquitous Language** — Method names come from the domain, not CRUD (`commitTo`, not `setStatus`) 3. **Small Aggregates** — Root + Value Objects by default; add child Entities only for true invariants 4. **One transaction = one Aggregate** — Cross-Aggregate rules use eventual consistency via Domain Events 5. **Reference by ID** — Never hold object references to other Aggregates 6. **Value Objects first** — Use Entities only when individual identity is essential 7. **Domain Services sparingly** — Excessive services → anemic model 8. **Protect invariants** — The Aggregate is the last line of defence; never trust the caller --- ## Output Format When reviewing code, report: ``` ## Anemia Diagnosis: <ClassName> Severity: [None | Mild | Moderate | Severe] Issues: - <description of problem> Recommended refactoring: - <specific move from refactoring.md> ``` When refactoring, show a before/after diff for each class touched.
© tech-leads-club · MIT · tech-leads-club/agent-skills