naming-cheatsheet

Apply A/HC/LC naming conventions to variables, functions, and classes.

1|Updated Mar 20, 2026

Search Tags:#refactoring #readability #naming-conventions #code-review #naming #language-agnostic #ahc-lc

Ready to run

npx skills add https://github.com/Thomashighbaugh/opencode --skill naming-cheatsheet-thomashighbaugh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: naming-cheatsheet
Source: https://github.com/Thomashighbaugh/opencode/tree/main/skills/naming-cheatsheet
Command: npx skills add https://github.com/Thomashighbaugh/opencode --skill naming-cheatsheet-thomashighbaugh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Naming identifiers across codebases is inconsistent, ambiguous, and often hard to maintain; this guide provides a compact, language-agnostic approach to make variable and function names clear, memorable, and accurate about intent.

Core Features & Use Cases

Defines the S-I-D principles (short, intuitive, descriptive) to evaluate and improve names.
Presents the A/HC/LC pattern to structure actions, high context, and low context for function names and shows recommended verb/prefix usage and boundary naming.
Use cases include naming new variables and functions, performing code reviews focused on naming consistency, and guiding refactors or team style guides.
Example: when refactoring a component, apply the pattern to rename ambiguous identifiers into concise names that reveal action and context.

Quick Start

Apply the A/HC/LC pattern to rename ambiguous identifiers so they are short, intuitive, and descriptive in one file or across a code review.

Frequently Asked Questions about naming-cheatsheet

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

FAQPage Schema

How do I apply consistent naming conventions to variables and functions during a refactor?▼

Apply the language-agnostic A/HC/LC pattern to structure function names with action, high context, and low context. Evaluate identifiers using the S-I-D principles—short, intuitive, descriptive—to rename ambiguous variables into clear, concise names across your codebase.

What is the A/HC/LC pattern for code review naming consistency?▼

The A/HC/LC pattern structures identifiers by separating action, high context, and low context. It helps enforce prefix and verb rules, ensuring function names remain concise, intuitive, and descriptive while maintaining language-agnostic naming consistency during code reviews.

Can I use these naming rules for React hooks and language-agnostic codebases?▼

Yes, the naming conventions encode specific React hook naming constraints alongside general prefix and verb rules. They apply across programming languages and codebases, ensuring identifier clarity and consistency regardless of the specific framework or language used.

What's the best way to structure function names for readability across different programming languages?▼

Use the S-I-D principles to keep names short, intuitive, and descriptive, then apply the A/HC/LC pattern to define actions and context boundaries. This language-agnostic approach ensures function names reveal intent clearly across any programming language or team style guide.

When do I need singular vs plural naming for identifiers in my codebase?▼

Singular and plural usage depends on whether an identifier represents a single entity or a collection. The naming conventions define specific boundary rules for singular and plural forms, ensuring variables and functions accurately reflect their data structure and intent.

Why does inconsistent identifier naming make code maintenance difficult?▼

Inconsistent identifier naming creates ambiguity and obscures intent, making code hard to read and maintain. Applying language-agnostic conventions like the A/HC/LC pattern and S-I-D principles resolves this by producing concise, intuitive, and descriptive names that accurately communicate purpose.