Domain Modeling
Unified domain and data modeling for business entities, invariants, schema design...
Install
npx skills add rsmdt/the-startup --skill domain-modeling -g -a claude-code -y- Repository
- rsmdt/the-startup577
- Category
- Design
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 507 tokens
- Runs scripts
- No, instructions only
What it does
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 languagereference/tactical-patterns.md, Entities, value objects, aggregates, domain events, repositoriesreference/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.
