ubiquitous-language

To extract a domain-driven design glossary from project discussions, the Skill analyzes conversational input to identify domain-specific terminology, resolving semantic ambiguities by examining nouns and verbs to produce a canonical Markdown file.

A ubiquitous language glossary is a canonical collection of domain-specific terms shared by developers and domain experts. You need one during software architecture design and domain modeling to resolve communication gaps and prevent implementation errors caused by inconsistent terminology.

To detect conflicting terminology and synonyms during a project discovery phase, the Skill identifies and flags ambiguous terms, synonyms, and overloaded concepts, helping reconcile definitions of terms like "Order" and "Account" so the codebase reflects the actual business domain.

Yes, you can generate technical documentation in Markdown format from conversational input. The Skill performs structured analysis of conversations to produce a canonical glossary file in Markdown format, typically outputting the result to the docs directory.

The best way to resolve semantic ambiguities in domain modeling terminology is to perform structured analysis of nouns and verbs from domain expert conversations, extracting a canonical glossary that flags overloaded concepts and enforces a single, precise language across the team.

Inconsistent terminology causes technical debt in software architecture design because it creates communication gaps between developers and domain experts, leading to overloaded concepts and implementation errors where the codebase fails to reflect the actual business domain.