Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

naming-conventions | code-quality | ClaudePluginHub

Skill

naming-conventions

From code-quality

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

$

npx claudepluginhub sethdford/claude-skills --plugin engineer-code-quality

Popularity

Parent stars

13

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/code-quality:naming-conventions

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Art and science of selecting names that reveal intent and reduce cognitive load.

SKILL.md

46 lines · ~618 tokens

Similar Skills

naming-precision

12

Enforces precise naming for variables, functions, classes, files, and identifiers. Bans vague names like data/temp/result/info/handle/manager; promotes semantic accuracy and domain-specific terms via specificity ladder.

1 file

naming-analyzer

27

Suggests improved names for variables, functions, classes, files, DB tables, and API endpoints using language-specific conventions like camelCase or snake_case.

evolutionary-naming

57

Audits and improves poor code names via evolutionary process in audit or improve modes. Targets -Manager/-Util suffixes, single-letter vars, god methods.

3 files3 tools

evolutionary-naming

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Variables: Use full words; userAccount not acc; isActive not a
Functions: Use verb phrases; getUserById(), calculateInterest(), validateEmail()
Classes: Use noun phrases; User, PaymentProcessor, ValidationRule
Constants: Use SCREAMING_SNAKE_CASE; MAX_RETRIES, DEFAULT_TIMEOUT
Boolean Variables: Prefix with is, has, should; isValid, hasPermission, shouldRetry
Avoid Abbreviations: Unless ubiquitous (HTTP, URL); currentUser not currUsr
Scope Rule: Shorter names for tiny scopes (loop counters), longer for larger scopes
Domain Language: Use terms from the business domain; invoice not doc

Anti-Patterns

Using vague names ("manager", "processor", "handler") because they sound professional; these obscure actual intent
Abbreviating names to save keystrokes (IDEs do autocomplete anyway); idx instead of index hurts readability
Encoding type information in names (Hungarian notation iCount, strName); type systems exist for a reason
Using single-letter variables outside loop counters; for (int i = 0; ...) is fine, but e = x + y is not
Naming by external context rather than responsibility; getData() in a UserService is vague; getUserAccount() is clear

Further Reading

Robert C. Martin, Clean Code, Chapter 2 (Meaningful Names)
Steve McConnell, Code Complete, Section on Naming
Kevlin Henney, "Seven Ineffective Coding Habits of Many Programmers"