Skip to content
Back to skills

Project Domain

ASecurity

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

  • 416 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 7, 2026
developmenttypescriptpythongoapifrontend

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add aiskillstore/marketplace --skill project-domain --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Domain?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Domain
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-project-domain/badge)](https://www.skillsdirectory.com/skills/aiskillstore-project-domain)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-domain
description: "Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding."
generated_by: ai-dev-kit:recommend-skills
---

<!-- 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

Files in this skill

  • SKILL.md2.2 KB
  • skill-report.json8.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…