ddd-ubiquitous-language

One-line summary

Establish a single vocabulary shared by domain experts, developers, code, and tests — within one bounded context.

When to use this skill

• A new project starting to model a domain.
• Persistent terminology drift between business and engineering.
• The code's names don't match how domain experts talk.
• Translation tables sit between conversation and code ("when the business says 'invoice', we mean BillingDocument").

When NOT to use this skill

• Code-level pattern questions → delegate to tactical pattern skills.
• Cross-context terminology translation → route to ddd-context-mapping.
• Naming conventions for variables and functions in general → that is a code-style concern, not DDD.

Core content