aiskillstore {project} Domain Vocabulary
Domain model understanding and vocabulary patterns for this project.
Variables
| Variable | Default | Description |
|---|---|---|
| ENFORCE_TERMINOLOGY | true | Flag inconsistent term usage |
| RELATIONSHIP_DEPTH | 2 | Levels of entity relationships to trace |
Instructions
- Load domain entities from models
- Understand entity relationships
- Use consistent terminology
- Validate against domain rules
Red Flags - STOP and Reconsider
If you're about to:
- Use synonyms inconsistently (e.g., "user" vs "account" interchangeably)
- Create a model field that duplicates existing concepts
- Ignore relationship constraints
STOP -> Check glossary -> Verify relationships -> Then proceed
Domain Glossary
Core Entities
| Term | Definition | Model Location |
|---|---|---|
| [TODO] | [TODO] | [TODO] |
Entity Relationships
[TODO: Add entity relationship diagram or description]
Example:
User 1-* Orders
Order *-1 Product
Product *-* Category
Terminology Rules
Naming Conventions
| Concept | Correct Term | Avoid |
|---|---|---|
| [TODO] | [TODO] | [TODO] |
Status Fields
| Entity | Valid Statuses | Transitions |
|---|---|---|
| [TODO] | [TODO] | [TODO] |
Model Locations
Key models and their locations:
| Entity | Python Model | TypeScript Type | BAML Type |
|---|---|---|---|
| [TODO] | [TODO] | [TODO] | [TODO] |
Validation Rules
Business rules enforced at the domain level:
- [TODO: Add domain validation rules]
Integration
This skill integrates with:
- ORM models in
src/models/ - BAML types in
baml_src/ - API schemas
- Frontend types
Customization
Edit this file to add:
- New entity definitions
- Relationship changes
- Terminology rules
- Validation constraints