naming-convention

Enforce camelCase, UPPER_SNAKE_CASE, and lower_snake_case naming in JavaScript/TypeScript codebases.

2|Updated May 6, 2026

Search Tags:#typescript #camelcase #naming #config_parameters #ts-type-naming

Ready to run

npx skills add https://github.com/lonewolfyx/skills --skill naming-convention-lonewolfyx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: naming-convention
Source: https://github.com/lonewolfyx/skills/tree/main/skills/naming-convention
Command: npx skills add https://github.com/lonewolfyx/skills --skill naming-convention-lonewolfyx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent naming across a codebase leads to reduced readability, higher cognitive load for developers, and more bugs during maintenance and onboarding.

Core Features & Use Cases

Defines and enforces naming rules for functions (camelCase), variables (camelCase), constants (UPPER_SNAKE_CASE), and config parameters (lower_snake_case) to improve readability and maintainability.
Guides alignment with business context and usage scenarios across API layers, data models, utilities, and configuration.
Provides structured guidance for refactors and audits to ensure semantic accuracy and consistency throughout the project.

Quick Start

Run naming-convention to lint your codebase and auto-suggest identifier renames to conform.

Frequently Asked Questions about naming-convention

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

FAQPage Schema

How do I enforce consistent naming conventions for variables and constants in a TypeScript codebase?▼

To enforce consistent naming conventions in TypeScript, apply camelCase for functions and variables, UPPER_SNAKE_CASE for constants, and lower_snake_case for config parameters. This structured approach reduces cognitive load and improves codebase maintainability.

What is the best way to standardize config parameter naming and ts-type-naming across utility modules?▼

Standardizing config parameter naming involves applying lower_snake_case for config parameters and aligning ts-type-naming for interfaces and types. This ensures semantic accuracy and consistency across API layers, data models, and utility modules.

Can I auto-suggest identifier renames during a codebase audit for JavaScript projects?▼

Yes, you can auto-suggest identifier renames during a codebase audit to conform to JavaScript naming rules. It lints your codebase and provides structured guidance for refactors to ensure semantic accuracy throughout the project.

Does this naming standardization approach support API layers and data models or only core modules?▼

This naming standardization supports API layers, data models, utilities, and core modules. It guides alignment with business context and usage scenarios across your entire JavaScript or TypeScript project, not just isolated core modules.

Why use lower_snake_case for config parameters instead of camelCase in JavaScript projects?▼

Using lower_snake_case for config parameters distinguishes them from camelCase variables and functions. This explicit separation improves readability and reduces bugs during maintenance and onboarding by clarifying the identifier's role.