Does it flag single-letter variables?

It intelligently flags single-letter variables in large scopes where they hurt searchability, while allowing them in tiny scopes like loop counters where they are standard.

Why should I avoid names like 'manager' or 'handler'?

These are common anti-patterns that sound professional but obscure the specific responsibility of a class or function; this skill suggests more descriptive alternatives.

Can it help with domain-specific naming?

Yes, it encourages the use of business domain language (e.g., using 'invoice' instead of 'doc') to ensure code aligns with the actual business logic.

How does this skill improve code quality?

It identifies names that obscure intent and suggests replacements based on the 'reveal intent' principle, making the code self-documenting and easier for teams to maintain.

Which naming standards does this skill follow?

This skill is grounded in industry-standard practices from Robert C. Martin's Clean Code and Steve McConnell's Code Complete, ensuring professional-grade nomenclature.

Code Naming Conventions

Name: Code Naming Conventions
Author: sethdford

bysethdford

•

Herramientas para Desarrolladores

Enforces standards-based naming patterns to improve code readability and reveal developer intent.

This skill empowers Claude to identify and refactor poorly named variables, functions, and classes using industry-standard principles from Clean Code and Code Complete. By moving beyond vague identifiers like 'manager' or 'processor' and eliminating cryptic abbreviations, this skill helps developers create a self-documenting codebase. It reduces cognitive load for readers, simplifies debugging, and ensures that code remains highly searchable and maintainable throughout the software development lifecycle.

Características Principales

01Anti-Pattern Detection: Identifies and flags Hungarian notation, single-letter variables, and vague suffixes.

02Boolean Standardization: Enforces 'is', 'has', and 'should' prefixes for clearer logical evaluations.

035 GitHub stars

04Scope-Based Optimization: Applies shorter names for local scopes and descriptive, searchable names for global contexts.

05Domain-Language Alignment: Ensures code terminology matches business domain concepts over generic technical terms.

06Intent-Revealing Refactoring: Suggests names that explain 'why' a variable exists without extra comments.

Casos de Uso

01Conducting automated code reviews to ensure naming consistency across a growing team.

02Refactoring legacy codebases where cryptic variable names obscure the original logic.

03Modernizing codebase searchability by replacing non-descriptive identifiers with grep-friendly names.

Características Principales

01Anti-Pattern Detection: Identifies and flags Hungarian notation, single-letter variables, and vague suffixes.

02Boolean Standardization: Enforces 'is', 'has', and 'should' prefixes for clearer logical evaluations.

035 GitHub stars

04Scope-Based Optimization: Applies shorter names for local scopes and descriptive, searchable names for global contexts.

05Domain-Language Alignment: Ensures code terminology matches business domain concepts over generic technical terms.

06Intent-Revealing Refactoring: Suggests names that explain 'why' a variable exists without extra comments.

Casos de Uso

01Conducting automated code reviews to ensure naming consistency across a growing team.

02Refactoring legacy codebases where cryptic variable names obscure the original logic.

03Modernizing codebase searchability by replacing non-descriptive identifiers with grep-friendly names.