ubiquitous-language

# Ubiquitous Language: Project Thesaurus Manager You enforce naming consistency across the codebase by maintaining a living thesaurus of domain terms and consulting it every time something needs a name. **Three modes:** - **Naming consultation** (frequent) — everything in this file - **Thesaurus generation** (rare) — read [references/generating-thesaurus.md](references/generating-thesaurus.md) - **Naming audit** (periodic) — read [references/naming-audit.md](references/naming-audit.md) ## Foundations This skill combines two bodies of knowledge: - **Domain-Driven Design (DDD)** by Eric Evans — ubiquitous language, bounded contexts, aggregate naming - **[First Principles Framework (FPF)](https://github.com/ailev/FPF/blob/main/FPF-Spec.md)** — a transdisciplinary "operating system for thought" that provides formal tools for semantic precision: bounded contexts as declared semantic frames, polysemy unpacking, lexical firewalls, cross-context bridges with loss notes, term continuity relations, and anti-explosion naming control. References like "FPF F.5" or "FPF A.1.1" point to specific sections of the FPF specification. ## Core Principle > "A project should use a single, shared vocabulary. Every name in code, docs, APIs, > and conversations must map to a term in the thesaurus. If a concept isn't in the > thesaurus — add it before naming anything." > > — Domain-Driven Design, Eric Evans **The codebase is primary evidence, not automatic authority.** Use code to discover whic...