ubiquitous-language

A ubiquitous language glossary codifies domain terms into a single authoritative reference, preventing miscommunication across product, engineering, and documentation by resolving synonyms and establishing consistent terminology.

To create a canonical glossary, gather raw terms from code and conversations, resolve naming conflicts, and document the terms, aliases, definitions, and usage examples in a structured UBIQUITOUS_LANGUAGE.md file.

Resolve terminology conflicts by mapping synonyms extracted from project conversations and code sources, then establishing a single authoritative name for each concept in a living glossary to guide UI copy and PRDs.

The glossary uses a structured Markdown file named UBIQUITOUS_LANGUAGE.md, documenting each domain term alongside its aliases, definitions, and specific usage examples for code quality and docs.

Yes, the glossary process applies across existing Claude code sources, project conversations, and domain knowledge to surface raw terms, resolve aliases, and publish a living glossary that guides future development.

Build a glossary when domain miscommunication threatens code consistency, requiring the codification of terms from scattered product, engineering, and documentation sources into a centralized reference.