domain-modeling

To maintain a ubiquitous language glossary, use this skill to manage a centralized CONTEXT.md file that records canonical definitions and challenges vague terminology, ensuring technical implementation aligns with business concepts. It enforces consistent naming across the codebase through iterative refinement of context files.

Recording architectural decisions to prevent domain drift is best achieved through structured ADRs that document high-stakes technical trade-offs. This skill provides a disciplined approach to capturing these decisions, ensuring the team's shared language and code remain perfectly aligned over time.

To resolve terminology debates like Customer versus User, this skill forces a decision, records the chosen definition in a canonical glossary, and ensures the selected term is consistently applied across the codebase. It actively challenges ambiguous terminology to maintain alignment.

You need to document architectural decisions with ADRs when facing high-stakes technical trade-offs that impact the domain model. This skill enforces a structured approach to recording these decisions, preventing future ambiguity and ensuring alignment between business concepts and technical implementation.

Domain-driven design documentation requires consistent adherence to defined formatting standards for terminology management and ADRs. This skill maintains the project's domain model by enforcing these standards across context files, ensuring the canonical glossary and architectural decisions remain structured and accessible.