ubiquitous-language

You maintain a domain vocabulary glossary by progressively logging terms during design sessions, which generates a canonical UBIQUITOUS_LANGUAGE.md file at the project root to reduce ambiguity during domain modeling.

Ubiquitous language in domain-driven design is a shared, structured vocabulary used by developers and domain experts to reduce ambiguity. You need it during design interrogation sessions to ensure terms and definitions are consistently understood across a bounded context.

To log domain terms progressively, initiate a design session and supply emerging terms and definitions to the AI. The skill captures the domain vocabulary and maintains the canonical glossary by progressively appending entries to the UBIQUITOUS_LANGUAGE.md file.

Yes, you can resolve terminology conflicts using a finalization workflow that standardizes domain terms after modeling. This finalization step processes the captured domain vocabulary to resolve conflicts and finalize the canonical UBIQUITOUS_LANGUAGE.md glossary.

No specific dependencies or frameworks are required to document domain terminology. You only need to initiate a design session and supply domain terms and definitions to generate the structured UBIQUITOUS_LANGUAGE.md glossary file at your project root.

The best way to codify domain terms for bounded contexts is to progressively log vocabulary during domain modeling and use a finalization workflow to standardize terminology. This outputs a canonical UBIQUITOUS_LANGUAGE.md file resolving any design interrogation ambiguities.