domain-modeling · rsmdt — Claude Code skill: models and setup
The domain-modeling skill turns business rules into domain models, aggregate boundaries, and storage decisions. Use it when shaping a business model or changing schema consistency rules.
MIT ★ 587 updated 2026-10-26
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startupWhat domain-modeling does
The skill starts with business concepts and lifecycle states, separates core domain work from supporting concerns, then defines aggregates and enforceable invariants. It weighs strong consistency against eventual consistency and ties storage choices to how the system reads and writes data.
Its output covers bounded contexts, entities, value objects, aggregates, invariants, persistence, schema decisions, and a migration plan. For changes, it also considers compatibility, rollout, and rollback. Reference material under reference/ covers strategic and tactical patterns alongside consistency approaches. One firm constraint: business rules come before table and field mechanics, so storage convenience should not dictate domain correctness.
What it helps with
- split a domain into bounded contexts
- set aggregate boundaries around consistency needs
- turn business rules into enforceable invariants
- choose schema patterns for read and write behavior
- plan schema changes with compatibility and rollback
Example prompts for the agent
- Model the order and payment domain, including its invariants.
- Set aggregate boundaries for a subscription service.
- Plan a schema change that preserves compatibility and supports rollback.
How to install domain-modeling
1Plugin marketplace
/plugin marketplace add rsmdt/the-startup/plugin install team@the-startupThis installs the whole team plugin with all its skills
2Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill domain-modeling -a claude-code3Manually: put the files in place
~/.claude/skills/domain-modeling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/domain-modeling/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill domain-modeling -a codex2Manually: put the files in place
.agents/skills/domain-modeling/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill domain-modeling -a cursor2Manually: put the files in place
.cursor/skills/domain-modeling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rsmdt/the-startup plugins/team/skills/development/domain-modeling2Manually: put the files in place
.github/skills/domain-modeling/SKILL.md1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill domain-modeling -a gemini-cli2Platform CLI
gemini skills install https://github.com/rsmdt/the-startup --path plugins/team/skills/development/domain-modelingManually: put the files in place
.devin/skills/domain-modeling/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about domain-modeling
How do I install domain-modeling in Claude Code?
Add the marketplace with /plugin marketplace add rsmdt/the-startup, then install the plugin with /plugin install team@the-startup.
What does domain-modeling do?
It connects business concepts and consistency rules to data structures, producing an implementation-ready domain model. It also lays out schema choices and an evolution plan.
How does the skill handle data consistency?
It defines aggregates and invariants, then helps decide where strong consistency is required and where eventual consistency is acceptable.
Source text
SKILL.md · MIT
---
name: domain-modeling
description: Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.
---
## Persona
Act as a domain-modeling specialist who aligns business concepts, data structures, and consistency boundaries into an implementation-ready model.
**Modeling Target**: $ARGUMENTS
## Interface
DomainModel {
boundedContexts: string[]
entities: string[]
valueObjects: string[]
aggregates: string[]
invariants: string[]
persistenceStrategy: string
schemaDecisions: string[]
migrationPlan: string[]
}
State {
target = $ARGUMENTS
concepts = []
constraints = []
model = {}
}
## Constraints
**Always:**
- Model business rules before table/field mechanics.
- Define aggregate boundaries around consistency and transactional requirements.
- Make invariants explicit and enforceable.
- Choose schema patterns based on query and write behavior.
- Include schema/version evolution strategy for non-trivial changes.
**Never:**
- Let storage convenience override domain correctness.
- Introduce cross-aggregate transactions without clear necessity.
- Add denormalization/caching without read/write rationale.
## Reference Materials
- `reference/strategic-patterns.md` — Bounded contexts, context mapping, ubiquitous language
- `reference/tactical-patterns.md` — Entities, value objects, aggregates, domain events, repositories
- `reference/consistency-strategies.md` — Transactional (ACID), eventual consistency, saga pattern
## Workflow
### 1. Discover Domain Concepts
- Identify business capabilities, entities, and lifecycle states.
- Separate core domain from supporting concerns.
### 2. Define Consistency Boundaries
- Define aggregates and invariants.
- Decide where eventual vs strong consistency is acceptable.
### 3. Map to Persistence
- Select relational/document/key-value patterns per access path.
- Define schema structure, constraints, and indexing strategy.
### 4. Plan Evolution
- Define migration and compatibility strategy for changes.
- Identify rollout and rollback considerations.
### 5. Deliver Model
- Provide domain model, schema decisions, and implementation guidance.
© Rudolf S. · MIT · rsmdt/the-startup
Similar skills
SKILL.md skills catalog →domain-modeling by other authors comes first.