What problem does it solve? Naming decisions drift when agents follow generic training-corpus defaults, producing inconsistent vocabulary across code, docs, branches, commits, and UI copy. This Skill provides a canonical naming and wording doctrine so one concept keeps one name across every artifact. ## Core Features & Use Cases - Naming Precedence Workflow: Searches existing project vocabulary (AGENTS.md, CLAUDE.md, rg, git log) before inventing new terms, applying a clear precedence from user wording down to corpus defaults. - Cross-Artifact Doctrine: Covers code identifiers, branch and worktree names, commit subjects, PR titles and bodies, changelog entries, backlog and epic titles, and UI copy. - Mixed Dutch/English Rules: Keeps code names in English, preserves established technical terms in Dutch prose, and avoids literal translation of metaphor verbs. - Use Case: Before renaming a class, writing a commit subject, or titling a PR, consult the doctrine to pick a searchable, domain-accurate name free of agent or tooling signatures. ## Quick Start Ask the agent to review or propose a name for a class, branch, commit subject, or PR title using the naming doctrine before finalizing it.
