domain_model
Create a comprehensive domain model based on feature specifications and the technical constitution.
Best use case
domain_model is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a comprehensive domain model based on feature specifications and the technical constitution.
Teams using domain_model 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/domain_model/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How domain_model Compares
| Feature / Agent | domain_model | 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?
Create a comprehensive domain model based on feature specifications and the technical constitution.
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
# Domain Model Skill Design the system's core capabilities and boundaries. ## When to Activate This skill is relevant when: - Creating domain models from specifications - Defining system boundaries and entities - Establishing data structures and relationships - Synthesizing requirements into unified model ## Core Principles ### Bounded Contexts - Identify clear logical boundaries - Define specific responsibilities - Avoid context overlap - Maintain separation of concerns ### Ubiquitous Language - Terminology matches business domain - Consistent naming across specs - Use domain expert vocabulary - Align with product requirements ### Invariants Definition - Define rules that must always be true - Document core business constraints - Establish data integrity requirements - Define aggregate boundaries ### Constitution Compliance - Strict adherence to technical constitution - Follow established tech stack - Respect architecture patterns - Maintain security requirements ## Quick Checks When creating domain models, verify: - [ ] Technical constitution reviewed and followed - [ ] Product requirements (PRD) understood - [ ] All feature specifications analyzed - [ ] Executive summary provided - [ ] Bounded contexts identified and listed - [ ] Core aggregates and entities defined - [ ] Entity fields include: name, type, description - [ ] Storage references defined for all root entities - [ ] Invariants documented for key aggregates - [ ] Value objects defined for reusable structures - [ ] Domain services specified for complex operations - [ ] Event flows documented with diagrams - [ ] Tenant/user isolation strategy explicit - [ ] Audit logging strategy defined - [ ] Type definitions provided in project language - [ ] All entities traceable to requirements - [ ] Relationship to specifications mapped - [ ] Open design decisions clearly flagged - [ ] Resolved decisions include rationale
Related Skills
review_domain
Perform a thorough architectural review of a domain model.
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.
tech_review
Senior Principal Engineer performing thorough technical review of implementation plans before development.
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.
skeptical_review
Perform a critical, skeptical code review of the project from the perspective of a Principal Engineer.
security_agent
Perform a full security review of the codebase (Node.js & React focus).
review_plan
Review the technical implementation plan against the specification.
review_constitution
Review and stress-test the technical constitution after /constitute.
retro
Reflect on the completed feature, document lessons learned, and improve workflows.
release_gate
Final Go/No-Go check and release preparation.