| name | domain-model |
| description | Template for documenting domain model entities and relationships |
Domain Model
This skill provides domain model knowledge for the project.
How to Use
Document your project's domain model here to give agents context about:
- Entities: Core business objects and their purposes
- Relationships: How entities relate (1:1, 1:N, M:N)
- Business Rules: Validation constraints and invariants
- Field Descriptions: What each field means in business terms
- Enums/Value Objects: Status types, categories, codes
Template
Entity: [EntityName]
Purpose: [What this entity represents]
| Field | Type | Required | Description |
|---|
| id | Long/UUID | Yes | Primary key |
| name | String | Yes | [Business meaning] |
| status | Enum | Yes | [Possible values and meanings] |
| createdAt | DateTime | Yes | Record creation timestamp |
Relationships:
- Has many [OtherEntity] (via foreign key
entity_id)
- Belongs to [ParentEntity]
Business Rules:
- [Rule 1: e.g., "Status can only transition DRAFT -> ACTIVE -> ARCHIVED"]
- [Rule 2: e.g., "Name must be unique within parent scope"]
Adding Domain Knowledge
Replace this template with your actual domain model. The more detail you provide, the better agents can:
- Generate correct entity classes
- Write meaningful tests with realistic data
- Understand field mappings and transformations
- Validate business logic implementations