ubiquitous-language

To build a domain-driven design glossary, extract domain nouns, verbs, and concepts from your conversation, identify canonical terms, and flag synonyms or homonyms. This process formalizes ambiguous terminology into a consistent UBIQUITOUS_LANGUAGE.md file for review.

A ubiquitous language is a canonical glossary that harmonizes ambiguous domain terms across conversations. You need terminology management when domain nouns and verbs are inconsistently defined, causing conflicts and communication breakdowns in domain-driven design discussions.

To detect synonyms and flag ambiguities in domain terminology, analyze the active conversation to identify conflicting terms and homonyms. The glossary-building process surfaces these inconsistencies and records them in a concise summary of changes within the generated glossary file.

Yes, you can maintain a consistent glossary across multiple conversations by applying the extraction process iteratively. It identifies canonical terms, updates the UBIQUITOUS_LANGUAGE.md file in your working directory, and returns a concise summary of changes for ongoing glossary maintenance.

Yes, ubiquitous-language works without external dependencies or components. It independently extracts domain terminology from the current conversation, identifies canonical terms, and writes the resulting glossary directly to the working directory as a markdown file.

Domain terminology conflicts occur when synonyms and homonyms are used inconsistently across separate conversations. Extracting and formalizing these terms into a canonical glossary identifies ambiguities, harmonizes definitions, and prevents future communication breakdowns.