ubiquitous-language

Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file. Write a UBIQUITOUS_LANGUAGE.md file with this structure: Dev: "How do I test the sync service without Docker?" Domain expert: "Provide the filesystem layer instead of the Docker layer . It implements the same Sandbox service interface but uses a local directory as the sandbox ." Dev: "So sync-in still creates a bundle and unpacks it?" Domain expert: "Exactly. The sync service doesn't know which layer it's talking to. It calls exec and copyIn — the filesystem layer just runs those as local shell commands." When invoked again in the same conversation: - Scan the conversation for domain-relevant nouns, verbs, and concepts - Identify problems : - Same word used for different concepts (ambiguity) - Different words used for the same concept (synonyms) - Vague or overloaded terms - Propose a canonical glossary with opinionated term choices - Write to UBIQUITOUS_LANGUAGE.md in the working directory using the format below - Output a summary inline in the conversation - Be opinionated. When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid. - Flag conflicts explicitly. If a term is used ambiguously in the conversation, call it out in the "Flagged ambiguities" section with a clear recommendation.