the-art-of-naming

Name: the-art-of-naming
Availability: InStock
Author: kizzz

Enforce TypeScript and Angular naming conventions for variables, functions, and types.

Updated Aug 23, 2026

Search Tags:#typescript #readability #angular #coding-standards #naming #prefixes #casing

Ready to run

npx skills add https://github.com/kizzz/eleon-client --skill the-art-of-naming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: the-art-of-naming
Source: https://github.com/kizzz/eleon-client/tree/main/.agents/skills/the-art-of-naming
Command: npx skills add https://github.com/kizzz/eleon-client --skill the-art-of-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Naming consistency across a codebase is hard to achieve and maintain. This Skill provides a comprehensive guide to standardized naming for variables, functions, classes, interfaces, and types in TypeScript and Angular, improving readability and maintainability.

Core Features & Use Cases

Enforces Casing conventions (camelCase for variables and functions, PascalCase for types and classes, UPPER_CASE for exported constants)
Implements the S-I-D principle (Short, Intuitive, Descriptive) and bans contractions
Defines prefix and boolean naming rules, context duplication avoidance, and structured naming patterns (P/HC/LC for variables, A/HC/LC for functions)
Provides actionable guidance for code reviews, refactoring, linting, and onboarding to a codebase

Quick Start

Audit your codebase for naming inconsistencies and start renaming the riskiest identifiers to follow the rules.

Frequently Asked Questions about the-art-of-naming

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

FAQPage Schema

What are the standard naming conventions for TypeScript variables and functions?▼

Standard naming conventions for TypeScript variables and functions mandate camelCase, while types and classes use PascalCase and exported constants use UPPER_CASE. This casing standardization reduces ambiguity and improves codebase readability.

How do I apply the S-I-D principle when naming code identifiers?▼

To apply the S-I-D principle when naming code identifiers, ensure names are Short, Intuitive, and Descriptive while banning contractions. This structured pattern minimizes context duplication and enforces clear prefix and boolean naming rules.

What is the best way to standardize naming conventions across an Angular codebase?▼

The best way to standardize naming conventions across an Angular codebase is enforcing A/HC/LC patterns for functions and P/HC/LC patterns for variables. This ensures consistent identifiers during code reviews and refactors.

Does this naming convention approach work for both TypeScript interfaces and types?▼

Yes, this naming convention approach works for both TypeScript interfaces and types by enforcing specific casing, prefixes, and context duplication avoidance. It provides actionable guidelines for interface and type naming to improve maintainability.

How do I audit my codebase for naming inconsistencies and refactoring risks?▼

To audit your codebase for naming inconsistencies, review identifiers against S-I-D, casing, and prefix rules, then rename the riskiest variables and functions. This standardization process ensures faster onboarding and consistent identifiers.