review_domain
Perform a thorough architectural review of a domain model.
Best use case
review_domain is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Perform a thorough architectural review of a domain model.
Teams using review_domain should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review_domain/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review_domain Compares
| Feature / Agent | review_domain | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Perform a thorough architectural review of a domain model.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Review Domain Skill Conduct critical architectural review of domain models. ## When to Activate This skill is relevant when: - Domain model has been drafted - Need to validate architecture design - Checking constitution compliance - Verifying completeness and consistency ## Core Principles ### Skeptical Analysis - Assume things will break - Identify gaps proactively - Challenge assumptions - Look for edge cases ### Consistency Verification - Naming matches specifications - Types used consistently - Terminology aligned with domain - Standards applied uniformly ### Completeness Check - No "magic" entities undefined - All diagrams match text - Every reference resolved - No missing definitions ### Compliance Enforcement - Validate against technical constitution - Check data isolation requirements - Verify security constraints - Ensure audit requirements met ## Quick Checks When reviewing domain models, verify: - [ ] **Completeness**: All entities in diagrams defined in text - [ ] **Completeness**: All value objects defined - [ ] **Completeness**: No primitive obsession on complex fields - [ ] **Completeness**: Root entities have storage references - [ ] **Completeness**: Invariants defined for aggregates - [ ] **Constitution**: Tenant identifier on all relevant entities (if required) - [ ] **Constitution**: Access rules match isolation strategy - [ ] **Constitution**: Security paths consistent with requirements - [ ] **Constitution**: Audit trails defined for critical mutations - [ ] **Consistency**: Type names match domain terminology - [ ] **Consistency**: Timestamps consistently named - [ ] **Consistency**: Relationships clear with foreign keys defined - [ ] **Clarity**: Open design decisions are truly open - [ ] **Clarity**: MVP scope respected, no premature future-proofing - [ ] Issues grouped by severity (P1 Critical, P2 Major, P3 Minor) - [ ] Strengths acknowledged - [ ] Recommendations provided with code examples - [ ] Action items prioritized - [ ] Final decision: Approve or Request Changes
Related Skills
tech_review
Senior Principal Engineer performing thorough technical review of implementation plans before development.
skeptical_review
Perform a critical, skeptical code review of the project from the perspective of a Principal Engineer.
review_plan
Review the technical implementation plan against the specification.
review_constitution
Review and stress-test the technical constitution after /constitute.
domain_model
Create a comprehensive domain model based on feature specifications and the technical constitution.
code_review
Thorough code review focusing on security, quality, and maintainability. Reviews implementation against plan and best practices.
wireframe
Create markdown wireframes with detailed UX descriptions from a product specification. Senior UX Designer perspective inspired by Notion and Linear.
ux_redesign
Redesign a feature or page from a Principal UX Designer's perspective.
tasks
Break down an approved implementation plan into specific, actionable tasks.
specify
Create a product specification that defines what to build and why, without prescribing how.
security_agent
Perform a full security review of the codebase (Node.js & React focus).
retro
Reflect on the completed feature, document lessons learned, and improve workflows.