Applies specification-grade vocabulary when naming code symbols, files, commands, and interface text.
npx skills add https://github.com/sndrgrdn/skills --skill precise-naming-sndrgrdn
Please help me install this Agent Skill. Skill: precise-naming Source: https://github.com/sndrgrdn/skills/tree/main/precise-naming Command: npx skills add https://github.com/sndrgrdn/skills --skill precise-naming-sndrgrdn
push_dashboards.sh or "You're in!" that confuse engineers and users. This Skill enforces precise, professional vocabulary so every name denotes the actual domain concept, operation, or state. ## Core Features & Use Cases - Symbol and File Naming: Renames code symbols, files, and directories with literal, exact terms (e.g., deploy_dashboards.sh instead of push_dashboards.sh). - Interface and Status Text: Rewrites UI labels, statuses, and events in formal register (e.g., "Registration Complete" instead of "You're in!"). - Commit and Branch Naming: Applies the same specification-grade standard to commits, branches, and commands. - Use Case: While refactoring a payments module, rename Move Money to Transfer Funds and update all related events, statuses, and interface text to match the formal domain vocabulary. ## Quick Start Review the names in this module and rename any vague or casual symbols, files, and interface text using precise professional vocabulary.High-intent search queries and answers about installing and using this skill.
Name the actual domain concept, operation, or state using precise professional vocabulary an engineer would put in a formal specification. Prefer literal denotation over slang or metaphor, and use the shortest exact name, such as `deploy_dashboards.sh` instead of `push_dashboards.sh`.
It is the register a careful engineer would use in a formal specification, sometimes called the 1972 IBM engineer test. It defines tone rather than a historical word limit, so established technical terms remain valid while casual chat phrasing is rejected.
Yes, the same standard covers interface text, statuses, events, commits, and branches. For example, use "Registration Complete" instead of "You're in!" and "System Failure" instead of "Something is broken".
Avoid cute or clever metaphors whenever a literal term exists for the concept. Metaphors obscure meaning for new readers and translators, while literal names like "Transfer Funds" communicate the operation immediately.
Yes, established technical terms remain valid because the standard defines register, not a restricted historical vocabulary. The goal is precision and professionalism, not avoiding modern terminology.
apexradiusRenames plan files and code symbols with git-aware safety checks.
bordenetVerify renamed fields and API contracts across service boundaries.
mastra-aiReviews pull requests against code quality standards and a style guide.
eencinasqExtracts domain terminology from business documents into a ubiquitous language dictionary.