Skill

domain-modeling

Domain-Driven Design: aggregates, bounded contexts, ubiquitous language, value objects, domain events, repository pattern, anti-corruption layer. When to use DDD vs simple CRUD. Entity vs value object distinction. TypeScript implementations with invariant enforcement. Use when designing domain model for complex business logic, bounded context mapping.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Designing domain model for complex business logic

Supporting Assets

assets/domain-model-template.mdreferences/aggregate-design.mdreferences/ddd-decision-guide.mdreferences/ddd-strategic.mdreferences/domain-glossary.mdreferences/event-driven-integration.mdreferences/event-storming.mdreferences/term-conflict-resolution.mdreferences/ubiquitous-language.md

SKILL.md

Similar Skills

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

everything-claude-code

156.2k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

agent-introspection-debugging

Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

domain-modeling

Core principles

Ubiquitous language is the contract — code names must match business terms; if business says "Invoice", your class is Invoice, not Bill or Document

Aggregates enforce invariants — all business rules for a cluster of objects enforced by the root

Value objects are immutable — Money, Email, Address: no identity, defined by value

Domain events record facts — OrderCancelled not cancelOrder(), past tense

DDD is overkill for CRUD — if it's just data in / data out, use simple CRUD; DDD pays off when business rules are complex

References available

references/ddd-strategic.md — bounded context mapping, context map patterns, ACL implementation

references/ddd-decision-guide.md — DDD vs CRUD decision tree, subdomain classification, team topology alignment

references/event-driven-integration.md — events over sync calls, transactional outbox pattern, event versioning

references/event-storming.md — workshop facilitation guide, sticky note vocabulary, phases 1-7

references/aggregate-design.md — command/event/rule structure, read model derivation, event storming discoveries

references/ubiquitous-language.md — naming convention rules, element type table, what to avoid

references/domain-glossary.md — glossary entry format, e-commerce examples, maintenance cadence

references/term-conflict-resolution.md — 5-step conflict resolution protocol, cross-context disambiguation

Domain Modeling (DDD)

When to use

Designing domain model for complex business logic
Identifying bounded contexts and aggregate roots
Translating business rules into code invariants
Deciding between entities and value objects
Mapping existing code to DDD building blocks

Core principles

Ubiquitous language is the contract — code names must match business terms; if business says "Invoice", your class is Invoice, not Bill or Document
Aggregates enforce invariants — all business rules for a cluster of objects enforced by the root
Value objects are immutable — Money, Email, Address: no identity, defined by value
Domain events record facts — OrderCancelled not cancelOrder(), past tense
DDD is overkill for CRUD — if it's just data in / data out, use simple CRUD; DDD pays off when business rules are complex

References available

references/ddd-strategic.md — bounded context mapping, context map patterns, ACL implementation
references/ddd-decision-guide.md — DDD vs CRUD decision tree, subdomain classification, team topology alignment
references/event-driven-integration.md — events over sync calls, transactional outbox pattern, event versioning
references/event-storming.md — workshop facilitation guide, sticky note vocabulary, phases 1-7
references/aggregate-design.md — command/event/rule structure, read model derivation, event storming discoveries
references/ubiquitous-language.md — naming convention rules, element type table, what to avoid
references/domain-glossary.md — glossary entry format, e-commerce examples, maintenance cadence
references/term-conflict-resolution.md — 5-step conflict resolution protocol, cross-context disambiguation

Assets available

assets/domain-model-template.md — aggregate skeleton, value object template, repository interface template