Workspace Domain Glossary
Purpose
Maintains a single source of truth for business terminology. This ensures that designers, developers, and stakeholders mean the same thing when using specific terms.
When to use this skill
- •When writing or reviewing specifications
- •During migration of complex business logic
- •When detecting conflicting terminology in code or docs
Glossary Steps
- •Extract Domain Terms: Identify nouns and concepts unique to this business domain.
- •Define Canonical Meanings: Create one-sentence definitions that are universally accepted.
- •Detect Conflicting Usage: Flag cases where different terms are used for the same concept (e.g., "Customer" vs "User" vs "Client").
- •Enforce Consistency: Update code, specs, and docs to use the canonical term.
Decision Tree
mermaid
flowchart TD
A[New Term Detected] --> B{In Glossary?}
B -->|Yes| C[Apply Definition]
B -->|No| D{Synonym Exists?}
D -->|Yes| E[Redirect to Canonical Term]
D -->|No| F{Critical Term?}
F -->|Yes| G[Propose New Glossary Entry]
F -->|No| H[Use standard language]
Review Checklist
- •Precision: Is the definition narrow enough to avoid confusion?
- •Universality: Is this term used the same way across all components?
- •Justification: Is there a strong reason for this naming choice?
- •Simplicity: Avoid jargon where plain language works.
How to provide feedback
- •Be specific: "Term 'AccountExpiry' is used here, but glossary defines 'SubscriptionEnd'."
- •Explain why: "Using multiple terms for the same concept increases cognitive load for maintainers."
- •Suggest alternatives: "Recommend replacing 'AccountExpiry' with 'SubscriptionEnd' to match the domain glossary."
Never invent new terms without justification.