Skip to content

nledford/engineering-review-board / skills/domain-modeling

domain-modeling

Verified

Review tactical DDD models, aggregates, entities, value objects, invariants, domain services, and ubiquitous language. Use for a focused audit of an existing domain model; do not use to design a new model or force DDD onto simple data-centric work.

FileKindSize
SKILL.mdskill md1.5 KB
---
name: domain-modeling
description: Review tactical DDD models, aggregates, entities, value objects, invariants, domain services, and ubiquitous language. Use for a focused audit of an existing domain model; do not use to design a new model or force DDD onto simple data-centric work.
---

# Domain Modeling Skill

Use this skill as a tactical domain-model review lens. Always load
[`review-verification-protocol`](../review-verification-protocol/SKILL.md)
before reporting findings. For repository change reviews, also load
[`code-review`](../code-review/SKILL.md).

Use [`domain-driven-design`](../domain-driven-design/SKILL.md) when the primary
task is discovering or implementing a model rather than reviewing one.

## Workflow

1. Identify the bounded context, ubiquitous language, business rules, and
   lifecycle boundaries represented by the code.
2. Review entities, value objects, aggregates, repositories, services, and
   events against those rules rather than against pattern names alone.
3. Verify consistency boundaries, ownership, identity, state transitions, and
   whether domain APIs protect invariants.
4. Look for primitive obsession, anemic behavior, invalid intermediate states,
   and DTO, framework, or persistence leakage.
5. Confirm that suggested modeling complexity is justified. Record missing
   evidence, skipped validation, and residual domain risk.

## Output

Map verified issues to domain concepts, affected files, business risk, the
smallest useful refactor, skipped validation, and residual risk.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall