domain-modeling

To maintain ubiquitous language across a multi-context repository, use this skill to manage a centralized glossary in CONTEXT.md, enforcing consistent terminology and challenging vague definitions.

The best way to document architectural decisions for domain-driven design is using Architectural Decision Records (ADRs), which this skill structures to record high-stakes design trade-offs and clear rationale.

To resolve terminology drift between a conceptual model and implementation, enforce a rigorous shared vocabulary by defining canonical terms in a glossary and ensuring the codebase reflects those choices.

Yes, this domain modeling approach requires adherence to specific Markdown formats for context definitions and ADRs to ensure long-term maintainability across single or multi-context repositories.

You should use an architectural decision record when documenting high-stakes design trade-offs and critical architectural choices, providing a structured framework for clear rationale rather than informal notes.