naming

Evaluate identifiers to enforce consistent naming across codebases.

20|3|Updated Aug 16, 2016
One-click install
npx skills add https://github.com/heyJordanParker/dotfiles --skill naming-heyjordanparker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming
Source: https://github.com/heyJordanParker/dotfiles/tree/main/claude/.claude/skills/naming
Command: npx skills add https://github.com/heyJordanParker/dotfiles --skill naming-heyjordanparker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Naming is the foundation of readable code. This skill enforces consistent, descriptive identifiers to reduce confusion and maintenance overhead across projects and languages.

Core Features & Use Cases

  • Hierarchy of Authority: prioritize project conventions, then language/framework norms, then the skill's own rules to resolve naming decisions.
  • Core Rules: avoid ALL_CAPS (except PHP defines as needed), spell words out, context informs naming, no redundant suffixes, and hide implementation details.
  • Semantic Patterns: apply booleans with is/has/can/should prefixes; use verb+noun patterns for actions; ensure proper pluralization based on containers; consider transformers and accessors naming.
  • Checklist: verify no abbreviations (except common ones), minimize redundancy, and ensure names convey intent.

Quick Start

Rename a sample identifier 'MyVariable' to a compliant, descriptive name like 'myVariable' following the skill's naming rules.

Frequently Asked Questions about naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent naming conventions for variables and functions across my codebase?

Enforce consistent naming conventions by evaluating identifiers against a hierarchy of authority: prioritize project conventions, then language norms, then rules like avoiding abbreviations and redundant suffixes to ensure maintainability.

What are the best practices for naming booleans and action functions in code?

Best practices for naming booleans involve using is/has/can/should prefixes, while action functions should use verb+noun patterns to ensure identifiers convey intent and improve overall code readability.

Does this naming convention approach work across different programming languages and projects?

This approach works across different languages and projects by applying a hierarchy of authority, prioritizing existing project conventions and framework norms before applying its own universal identifier rules.

How do I rename identifiers to hide implementation details and reduce code redundancy?

Rename identifiers to hide implementation details by removing redundant suffixes, spelling words out instead of using abbreviations, and ensuring names convey intent without exposing underlying logic.

When should I avoid using ALL_CAPS when defining variables and classes?

Avoid using ALL_CAPS for variables and classes except for specific cases like PHP defines, as standard naming conventions prefer spelling words out to improve code readability and maintainability.