project-domain
"Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding."
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
"Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding."
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generic BAML patterns for type-safe LLM prompting. Covers schema design, DTO generation, client wrappers, and cross-language codegen. Framework-agnostic.
Browser automation for documentation discovery. Use when curl fails on JS-rendered sites, when detecting available browser tools, or when configuring browser-based documentation collection.
C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.
Debug and analyze web applications using Chrome DevTools MCP. Use for console log inspection, network request monitoring, performance analysis, and debugging authenticated sessions. For basic browser automation (screenshots, form filling), use browser-discovery skill instead.
Patterns and techniques for analyzing brownfield codebases. Use when onboarding to unfamiliar code, preparing for refactoring, conducting architecture reviews, or identifying technical debt.
Detect new imports in modified files and auto-install missing dependencies. Works with npm, uv, pip, cargo, go mod, and other package managers. Triggers after code implementation to keep manifests in sync.
| name | {project}-domain |
| description | "Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding." |
Domain model understanding and vocabulary patterns for this project.
| Variable | Default | Description |
|---|---|---|
| ENFORCE_TERMINOLOGY | true | Flag inconsistent term usage |
| RELATIONSHIP_DEPTH | 2 | Levels of entity relationships to trace |
If you're about to:
STOP -> Check glossary -> Verify relationships -> Then proceed
| Term | Definition | Model Location |
|---|---|---|
| [TODO] | [TODO] | [TODO] |
[TODO: Add entity relationship diagram or description]
Example:
User 1-* Orders
Order *-1 Product
Product *-* Category
| Concept | Correct Term | Avoid |
|---|---|---|
| [TODO] | [TODO] | [TODO] |
| Entity | Valid Statuses | Transitions |
|---|---|---|
| [TODO] | [TODO] | [TODO] |
Key models and their locations:
| Entity | Python Model | TypeScript Type | BAML Type |
|---|---|---|---|
| [TODO] | [TODO] | [TODO] | [TODO] |
Business rules enforced at the domain level:
This skill integrates with:
src/models/baml_src/Edit this file to add: