Naming Conventions

Choosing meaningful, pronounceable names that reveal intent for functions, variables, classes, and modules.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill naming-conventions
Manual install
git 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-conventions

Personal 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
Read the full skill on GitHub

Details

Skill name
naming-conventions
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

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.