Naming Conventions
Choosing meaningful, pronounceable names that reveal intent for functions, variables, classes, and modules.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill naming-conventionsgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/code-quality/skills/naming-conventions ~/.claude/skills/naming-conventionsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Naming Conventions Art and science of selecting names that reveal intent and reduce cognitive load. ## Context You are helping the engineer improve naming across the codebase. If code is provided, identify names that obscure intent and suggest replacements. Names are the primary interface between code and readers. ## Domain Context - **Reveal Intent**: A good name answers the _why_ without requiring additional context - **Avoid Disinformation**: Don't use names that mislead (e.g., `accounts` for a single account) - **Make Meaningful Distinctions**: `a1`, `a2`, `a3` are meaningless; `source`, `target`, `result` are distinct - **Pronounceability**: Names you can say aloud are easier to discuss and remember - **Searchability**: Use searchable names; single-letter variables make grep useless ## Instructions 1. **Variables**: Use full words; `userAccount` not `acc`; `isActive` not `a` 2. **Functions**: Use verb phrases; `getUserById()`, `calculateInterest()`, `validateEmail()` 3. **Classes**: Use noun phrases; `User`, `PaymentProcessor`, `ValidationRule` 4. **Constants**: Use SCREAMING_SNAKE_CASE; `MAX_RETRIES`, `DEFAULT_TIMEOUT` 5. **Boolean Variables**: Prefix with `is`, `has`, `should`; `isValid`, `hasPermission`, `shouldRetry` 6. **Avoid Abbreviations**: Unless ubiquitous (HTTP, URL); `currentUser` not `currUsr` 7. **Scope Rule**: Shorter names for tiny scopes (loop counters), longer for larger scopes
Details
- Skill name
naming-conventions- Repository
- sethdford/claude-skills
- Path
engineer/code-quality/skills/naming-conventions/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Naming Conventions skill do?
Choosing meaningful, pronounceable names that reveal intent for functions, variables, classes, and modules.
How do I install the Naming Conventions skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Naming Conventions popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Network Segmentation
48sethdford/claude-skills
Design and implement network segmentation to limit lateral movement and contain breaches.
Multi Region Design
48sethdford/claude-skills
Distribute globally across multiple regions for low latency, compliance, and resilience. Plan data replication, failover, and latency optimization. Use when designing global systems.
North Star Vision
48sethdford/claude-skills
Articulate a compelling north-star product vision that aligns teams and inspires strategic design decisions.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.