How does it handle boolean naming?

It enforces a question-based prefix pattern (is, has, can, should, will) to ensure that boolean variables and functions read like clear yes/no questions.

Is this naming skill specific to a particular programming language?

No, these principles are language-agnostic and apply to any modern programming environment including TypeScript, Python, Go, Rust, and Java.

Why are 'Manager' and 'Helper' suffixes discouraged?

These terms are often 'Ousterhout red flags' that indicate a lack of clear responsibility. This skill encourages specific names like 'Processor', 'Validator', or 'Formatter' to force better design thinking.

Does this skill work with framework-specific patterns?

While it prioritizes domain language, it includes context-aware exceptions for established framework patterns like Repository, Factory, or Controller when they add specific meaning.

Can this skill help with existing legacy code?

Yes, it is highly effective for refactoring tasks, helping Claude identify vague names and replace them with clear, domain-specific terminology.

Naming Conventions Expert

Name: Naming Conventions Expert
Author: phrazzld

byphrazzld

•

Developer Tools

Enforces universal, intention-revealing naming principles across all programming languages to improve code clarity and maintainability.

About

This skill empowers Claude to act as a rigorous code reviewer and architect, ensuring that variables, functions, and classes follow domain-driven naming standards rather than technical implementation details. By prohibiting vague terms like 'Manager' or 'Helper' and promoting intention-revealing patterns like verb-noun functions and question-prefixed booleans, it helps developers eliminate architectural 'red flags' and create self-documenting codebases. Whether you are refactoring legacy logic or starting a new project, this skill ensures your naming reflects clear design thinking and business logic across any stack, including TypeScript, Go, Rust, and Python.

Key Features

Standardizes boolean patterns using is/has/can/should prefixes
Enforces intention-revealing variable and function names
Promotes domain-specific language over implementation-based naming
Eliminates vague suffixes like Manager, Helper, and Util
Applies language-agnostic principles to any programming environment
2 GitHub stars

Use Cases

Establishing a consistent, professional naming standard for new multi-language projects
Automated code reviews to identify and correct 'naming smells' before merging
Refactoring legacy codebases for better readability and architectural clarity

About

Key Features

Standardizes boolean patterns using is/has/can/should prefixes
Enforces intention-revealing variable and function names
Promotes domain-specific language over implementation-based naming
Eliminates vague suffixes like Manager, Helper, and Util
Applies language-agnostic principles to any programming environment
2 GitHub stars

Use Cases

Establishing a consistent, professional naming standard for new multi-language projects
Automated code reviews to identify and correct 'naming smells' before merging
Refactoring legacy codebases for better readability and architectural clarity