ddd-architecture
Skill34 starsChanged 10 days agoMITView on GitHub
Domain-Driven Design for complex business domains. Use when deciding whether DDD is warranted, defining bounded contexts, aggregates, entities and value objects, applying CQRS or domain events, or organizing a domain layer. .NET project and solution layout is dotnet-solution-architect.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Hive-Academy/ptah-extensionword for word, first seen Nov 3, 2026
- troskater/flowdeck-claudetheir own version, first seen Oct 25, 2026
- Gvidon-Solutions/agentops-backend-kittheir own version, first seen Oct 11, 2026
Other versions3 projects use a version of this.
Word for word · 1
- Hive-Academy/ptah-extension★ 34100% same
Edited · 0
None found.
Wrote their own version · 2
- Gvidon-Solutions/agentops-backend-kit★ 0same name
- troskater/flowdeck-claude★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-lanesSkill
- angular-3d-scene-crafterSkill
- angular-frontend-patternsSkill
- angular-gsap-animation-crafterSkill
- execute-phase-gated-taskSkill
- frontend-designSkill
- humanize-librarySkill
- nestjs-backend-patternsSkill
- nestjs-deploymentSkill
- nx-workspace-architectSkill
- orchestrationSkill
- ptah-surface-authoringSkill
- resilient-nestjs-patternsSkill
- saas-platform-patternsSkill
- saas-workspace-initializerSkill
- session-handoffSkill
- skill-creatorSkill
- technical-content-writerSkill
- tribunalSkill
- ui-ux-designerSkill
- webhook-architectureSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If this skill is invoked from saas-workspace-initializer Step a2, the Round 1 discovery answers (jobs-to-be-done, candidate domains, MVP …
- Distinctive: line 22
Do entities have complex lifecycles?
- Distinctive: line 24
Do different parts of the system use different terminology?
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Domain-Driven Design Architecture
Decide whether DDD is warranted, then load the one reference that owns the pattern. Do not implement a base class or a library layout from this file.
When to Engage User
DDD is highly context-dependent. ALWAYS discuss with user before implementing.
If this skill is invoked from saas-workspace-initializer Step a2, the Round 1 discovery answers (jobs-to-be-done, candidate domains, MVP scope) are already available — use them and do not re-ask the equivalent questions. Ask only what those answers leave open.
Load references/discovery.md only when domain discovery is still open.
Warrant
Score with the user before writing pattern code. Count the yeses:
- Do entities have complex lifecycles? (draft → approved → fulfilled)
- Are there business rules that span multiple entities?
- Do different parts of the system use different terminology?
- Is there a need for audit trails or event sourcing?
- Will multiple teams work on different parts?
| Yeses | Do |
| 0-1 | Simple services. Stop. |
| 2-3 | Tactical patterns only (entities, value objects). |
| 4-5 | Strategic DDD: bounded contexts, then the tactical patterns. |
Situations the score alone does not route:
| Situation | Do |
| Simple CRUD | Same as 0-1. Skip DDD. |
| Multiple teams | Bounded contexts, even when the rest of the score is low. |
| High consistency needs | Aggregates + domain events. Load entities-aggregates.md and domain-events.md. |
Rules that break silently
- Copy
Entity,EntityId, andValueObjectfrom the references below. Do not hand-roll a base class. - One aggregate per transaction; refer to other aggregates by id. Home: references/entities-aggregates.md.
References
| Load | When |
| references/discovery.md | Domain discovery is still open. |
| references/entities-aggregates.md | Writing an entity, an identity type, or an aggregate. |
| references/value-objects.md | Writing a value object. |
| references/cqrs-pattern.md | Separating commands from queries, or a read path dominates. |
| references/domain-events.md | Recording what happened, eventual consistency, or an audit trail. |
| references/repository-pattern.md | Persisting an aggregate. |
| references/layer-layout.md | Organizing a domain library into folders. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.