ubiquitous-language

Build a ubiquitous language glossary by extracting domain-specific terminology and definitions from conversational context to identify ambiguities, synonyms, and canonical term mappings. The skill processes project-level discussions to formalize domain language into a persistent Markdown file.

Resolving terminology conflicts involves flagging ambiguous terms and identifying overloaded synonyms to prevent implementation errors. The skill analyzes conversation history to map canonical terms, ensuring developers and domain experts speak the same language and preventing logic bugs.

Extracting domain modeling terms from conversation history is the core function of this skill. It automatically identifies domain-relevant nouns and verbs from project discussions to build a formal, canonical glossary for domain-driven design clarity.

Maintain a persistent project glossary file by generating structured output in Markdown format. The skill extracts canonical terminology mappings from your project context and saves the glossary directly to the project root for ongoing reference.

No dependencies or components are required to extract a domain language glossary. The skill operates directly on your conversational context and project-level domain modeling tasks to identify canonical terms, synonyms, and ambiguities without external tooling.