naming-cheatsheet

Apply the A/HC/LC pattern to standardize identifier naming across languages.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/suwandre/my-opencode-config --skill naming-cheatsheet-suwandre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-cheatsheet
Source: https://github.com/suwandre/my-opencode-config/tree/main/skills/naming-cheatsheet
Command: npx skills add https://github.com/suwandre/my-opencode-config --skill naming-cheatsheet-suwandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Naming inconsistencies in codebases make maintenance harder and slow down onboarding. The A/HC/LC naming pattern provides a language-agnostic framework to produce clear, expressive identifiers.

Core Features & Use Cases

  • Enforces a consistent naming scheme for variables, functions, and classes across languages.
  • Helps teams rename ambiguous identifiers during refactors and code reviews to improve readability.
  • Serves as a quick reference guide for developers when designing new APIs or components.

Quick Start

Name a new identifier using the A/HC/LC pattern to ensure clarity and contextual meaning.

Frequently Asked Questions about naming-cheatsheet

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

FAQPage Schema
What is the A/HC/LC pattern for standardizing variable and function naming conventions?

The A/HC/LC pattern is a language-agnostic naming framework that structures identifiers using prefix, word boundary, and context guidelines to produce clear, expressive variables, functions, and classes for improved code readability.

How do I enforce consistent naming conventions for variables and functions across different programming languages?

You can enforce consistent naming conventions across any programming language by applying the A/HC/LC pattern, which provides language-agnostic guidelines for prefixes, word boundaries, and context-appropriate identifier naming.

Can I use the A/HC/LC naming pattern during code reviews and refactoring to improve code readability?

Yes, the A/HC/LC naming pattern can be applied during code reviews, refactors, and onboarding to rename ambiguous identifiers, reduce ambiguity, and ensure consistent maintainability across the codebase.

What's the best way to reduce ambiguity when designing new API component names?

The best way to reduce ambiguity in new API components is using the A/HC/LC pattern as a quick reference guide, ensuring contextual meaning and clear identifier design through standardized prefix and word boundary rules.

Does the A/HC/LC naming convention work with any programming language or tech stack?

Yes, the A/HC/LC naming convention is fully language-agnostic, meaning it works across any programming language and tech stack to enforce a consistent naming scheme for variables, functions, and classes.