Skill

naming-conventions

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

Install

Run in your terminal

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

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

ecc

140.7k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

ecc

140.7k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

ecc

140.7k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

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