Menu

Individual skill

ddd-architecture

0upvotes

Domain-Driven Design: bounded contexts, ubiquitous language, aggregates, and tactical patterns. Use when modeling complex domains or structuring domain logic.

skills/ddd-architecture/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# DDD Architecture

## Overview

Domain-Driven Design is **modeling software around the business domain** — building a shared
language with domain experts and letting that language shape the code. It's two things: strategic
design (bounded contexts, context mapping — where the big seams go) and tactical patterns
(aggregates, entities, value objects — how the model is built). DDD pays off in complex domains;
it's overhead in simple CRUD.

The through-line: the code should speak the business's language, and the boundaries should match
the business's reality.

## When to use
Back to top