multiAI Summary Pending

project-domain

Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding.

231 stars

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/project-domain/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/consiliency/project-domain/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/project-domain/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How project-domain Compares

Feature / Agentproject-domainStandard Approach
Platform SupportmultiLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding.

Which AI agents support this skill?

This skill is compatible with multi.

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

<!-- Generated by ai-dev-kit:recommend-skills on {date} -->
<!-- This skill can be safely deleted if no longer needed -->

# {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

1. Load domain entities from models
2. Understand entity relationships
3. Use consistent terminology
4. 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:

1. [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