skills.rest
frap129
frap129COMMUNITY
Explore all skills by this author →
WebsiteGitHub

naming-cheatsheet

Apply the A/HC/LC pattern to name variables, functions, and classes.

8|Updated Sep 7, 2021
Search Tags:#refactoring#coding#conventions#camelcase#naming#prefixes#a-hc-lc
One-click install
npx skills add https://github.com/frap129/dotfiles --skill naming-cheatsheet-frap129
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming-cheatsheet
Source: https://github.com/frap129/dotfiles/tree/main/.config/opencode/skills/naming-cheatsheet
Command: npx skills add https://github.com/frap129/dotfiles --skill naming-cheatsheet-frap129

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Naming inconsistency across codebases leads to confusion and reduced maintainability. This skill provides a clear, language-agnostic naming pattern to unify identifiers.

Core Features & Use Cases

  • Provides the A/HC/LC naming pattern to structure functions, methods, and variables.
  • Includes guidance on contextual order, prefixes, and English usage to improve readability.
  • Ideal for new projects, code reviews, and refactoring to elevate naming quality.

Quick Start

Name new functions and variables using the A/HC/LC pattern to ensure consistent, descriptive identifiers.

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 naming functions and variables?▼

The A/HC/LC pattern structures identifiers using prefixes, context, and logical components to create concise, descriptive names. It enforces consistent camelCase or chosen conventions for variables, functions, and classes across any language.

How do I standardize naming conventions during code refactoring?▼

Standardize naming during refactoring by applying the A/HC/LC pattern to ensure consistent, descriptive identifiers. This language-agnostic approach unifies prefixes and contextual order to improve readability and maintainability.

How do I structure clear and consistent names for new codebase projects?▼

Structure clear names for new projects by following the A/HC/LC pattern to define functions and variables. This enforces concise, descriptive identifiers with appropriate prefixes and consistent camelCase conventions.

Does this naming convention apply to multiple programming languages?▼

Yes, this naming convention applies to any programming language. It provides language-agnostic rules for applying consistent camelCase, appropriate prefixes, and descriptive context to unify identifiers across diverse codebases.

What are the limitations of using a structured naming pattern for identifiers?▼

A limitation of using a structured naming pattern is the strict adherence required to contextual order and prefix rules, which may require adjusting established naming habits during creation and review to maintain consistency.

Related Skills

Explore More Software Engineering Skills→
ValenBorrasValenBorras
1

coding-standards

Enforce naming, formatting, immutability, and React/TS patterns across projects.

Community
Advanced
stephanjstephanj
9

naming-analyzer

Analyze source code identifiers to enforce naming conventions across JavaScript, TypeScript, Python, Java, and Go.

Community
Intermediate
dev-khoidev-khoi

naming-cheatsheet

Standardize variable and function names using the A/HC/LC pattern.

Community
Basic
webdriveriowebdriverio
11

Global Coding Style

Enforce global coding style conventions across codebases during file creation or modification.

Official
Basic