domain-driven-design SKILL.md skillA

domain-driven-design from d-padmanabhan/agent-engineering-handbook is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add d-padmanabhan/agent-engineering-handbook/domain-driven-design@git:20260819.d23bb73

Pins git:20260819.d23bb73 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

d-padmanabhan/agent-engineering-handbook

Path

skills/domain-driven-design/SKILL.md

Versions recorded

1

Latest version

git:20260819.d23bb73, committed Aug 19, 2026

Size

6,752 bytes

Repository stars

20

License

MIT

Designs and reviews software domain models using Domain-Driven Design, including subdomains, bounded contexts, context maps, ubiquitous language, aggregates, value objects, domain events, repositories, and anti-corruption layers. Use when business rules are complex, service or module boundaries are unclear, teams disagree on terminology, or the user mentions DDD, bounded contexts, aggregates, or domain modeling.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Domain-Driven Design

Use Domain-Driven Design (DDD) to make complex business rules and ownership boundaries explicit. Do not use DDD vocabulary to disguise ordinary CRUD or technology-driven service decomposition.

## DDD Contract

- Start from business capabilities, policies, language, and change patterns, not tables, endpoints, or deployment units.
- Treat one model as valid only inside its bounded context. The same term may intentionally mean different things elsewhere.
- Use a ubiquitous language shared by domain experts and engineers in conversations, code, tests, APIs, and events.
- Align boundaries with cohesive invariants and ownership. A bounded context is a semantic and organizational boundary, not automatically a microservice.
- Keep aggregate boundaries small. One aggregate is one transactional consistency boundary.
- Reference other aggregates by stable identity rather than loading or mutating a large object graph.
- Make cross-context contracts explicit and versioned. Use an anti-corruption layer when an upstream model must not leak inward.
…

Read the whole file at its exact version.

How to install

mdr add d-padmanabhan/agent-engineering-handbook/domain-driven-design@sha256:b4fe2449768c201c

[![mdr](https://markdownregistry.com/badge/art_k2xkqrvb44ixle3c.svg)](https://markdownregistry.com/a/art_k2xkqrvb44ixle3c)

Versions

The registry has recorded 1 version of this file, committed on Aug 19, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_k2xkqrvb44ixle3c
GET https://markdownregistry.com/api/v1/resolve?ref=d-padmanabhan/agent-engineering-handbook/domain-driven-design
GET https://markdownregistry.com/api/v1/blob/b4fe2449768c201c2bf832b9dd05921a98c87c59647f188905e549754e7846de

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from d-padmanabhan/agent-engineering-handbook

Every file in d-padmanabhan/agent-engineering-handbook

Other files named domain-driven-design

Browse by kind, by grade A, or by owner.