# Standardize Project Domain Language

Teams lose time when models, APIs, and documentation use inconsistent business terms. This skill gives Claude, Codex, and Claude Code a shared domain glossary and relationship map.

## Install

```bash
npx skillstore add consiliency/project-domain
```

## Metadata

- Status: approved
- Slug: consiliency-project-domain
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4297ec4850638a76c59ed256fba52098127af6ba94cdb4017cf3b19600347a99
- Author: Consiliency
- GitHub username: Consiliency
- License: MIT
- Repository: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/stack-analyzer/templates/project-domain
- Ref: d11af420e07cd866fe39cfa937efef3223896c06
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/consiliency-project-domain
- Manifest: https://skillstore.pages.dev/api/skills/consiliency-project-domain/manifest

## Capabilities

- Defines a structure for core domain entities and model locations.
- Documents relationships between entities using a simple relationship section.
- Records preferred terminology and terms to avoid.
- Captures valid status values and allowed transitions.
- Links domain rules to ORM models, BAML types, API schemas, and frontend types.
- Gives assistants a checklist for terminology and relationship consistency.

## Use Cases

- Align Domain Terms: Create one reference for entity names, accepted terms, and terms that should not be used.
- Guide AI Code Changes: Give coding assistants project-specific language before they edit models, APIs, or frontend types.
- Review Model Relationships: Check that new fields, statuses, and relationships follow existing domain rules.

## Prompt Templates

### Fill the Glossary

```
Use the project-domain skill to draft glossary entries for the main entities in this project. Include definitions and model locations.
```

### Check Terminology

```
Review this proposed change with the project-domain skill. Flag inconsistent terms, duplicated concepts, and unclear entity names.
```

### Map Relationships

```
Use the project-domain skill to describe relationships between the affected entities. Include cardinality, ownership, and important constraints.
```

### Audit Domain Rules

```
Apply the project-domain skill to audit this feature design. Compare entity names, statuses, transitions, validation rules, and model locations.
```

## Limitations

- The template ships with TODO placeholders that must be filled for each project.
- It does not inspect source code or generate a glossary automatically.
- It depends on maintainers to keep relationships and validation rules current.
- It provides guidance, not runtime enforcement or schema validation.

## Best Practices

- Replace all TODO placeholders before relying on the skill for project work.
- Update the glossary whenever models, API schemas, or frontend types change.
- Keep definitions short and link each entity to its primary source location.

## Anti Patterns

- Using the template without adding project-specific entities or rules.
- Adding synonyms that hide duplicate concepts instead of choosing one term.
- Treating the skill as enforcement when validation still needs tests or schemas.

## Security Audit

- Audited at: 2026-07-06T07:49:26.787\+00:00
- Summary: The static findings are false positives caused by Markdown code fences, inline code formatting, and table headings in SKILL.md. No prompt injection, data exfiltration intent, or unsafe command execution evidence was found.

## Stats

- Views: 179
- Downloads: 8
- Favorites: 0
- Popularity score: 0