What problem does it solve?
It prevents ambiguous or misleading software names, UI text, and error messages by enforcing linguistic precision for meaning, audience register, and blame-free actionability.
Core Features & Use Cases
- Morphology for software artifacts: Guides how to form compounds, choose abbreviations responsibly, and align identifier/label structure with the artifact kind.
- Polysemy resolution: Forces ambiguous terms (e.g., provider, margin, shipping) to be qualified with domain-specific meaning to avoid comprehension failures.
- Register selection for audiences: Ensures end-user, agent, and developer-facing language uses the right tone, vocabulary density, and structure.
- Error-message linguistics: Applies a What → Why → What-to-do structure that is specific, blame-free, and action-oriented.
- Cross-cultural language awareness: Flags linguistic facts that affect global readability and i18n decisions (number structure, plural agreement, script direction, currency meaning).
Quick Start
Use the linguistics skill when you need to revise an identifier, UI label, or error message so its meaning is unambiguous for your intended audience.