skills.rest
site-bender
site-benderOFFICIAL
Explore all skills by this author →
GitHub

naming

Enforce casing rules and abbreviation standards for code identifiers.

Updated Aug 23, 2026
Search Tags:#best practices#code readability#naming conventions#screaming snake case#pascalcase#camelcase#kebab-case
One-click install
npx skills add https://github.com/site-bender/sitebender --skill naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming
Source: https://github.com/site-bender/sitebender/tree/main/.claude/skills/naming
Command: npx skills add https://github.com/site-bender/sitebender --skill naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill eliminates ambiguity and inconsistency in naming across the codebase, making code read like plain English. It significantly reduces cognitive load for developers, accelerates onboarding, and minimizes errors caused by misinterpretation, allowing your team to work more efficiently.

Core Features & Use Cases

  • Strict Casing Rules: Enforces camelCase, PascalCase, SCREAMING_SNAKE_CASE, and kebab-case for different identifier types (functions, types, constants, URLs).
  • "All Files Are index" Rule: Simplifies file naming by making the folder name carry semantic meaning, improving discoverability.
  • Abbreviation Management: Integrates with the abbreviations skill to ensure only approved, unambiguous abbreviations are used, preventing "decoding" effort.
  • Use Case: When naming a new function, this skill ensures you use camelCase (e.g., calculateOrderTotal). For a component, PascalCase (OrderSummary). For a constant, SCREAMING_SNAKE_CASE (MAX_ORDER_ITEMS). This consistency means you instantly know what an identifier represents just by its casing.

Quick Start

Explain the correct naming convention for a function named 'get user data' and a component named 'user profile'.