naming-conventions

Standardize file, directory, class, function, and variable naming across a codebase.

14|1|Updated Oct 23, 2025

Search Tags:#best practices #refactoring #clean code #readability #code style #code organization #naming conventions

Ready to run

npx skills add https://github.com/marcioaltoe/claude-craftkit --skill naming-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: naming-conventions
Source: https://github.com/marcioaltoe/claude-craftkit/tree/main/plugins/architecture-design/skills/naming-conventions
Command: npx skills add https://github.com/marcioaltoe/claude-craftkit --skill naming-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill ensures consistent, readable, and maintainable naming across the entire codebase. It eliminates ambiguity and confusion by providing clear guidelines for files, directories, classes, functions, and variables, improving collaboration and reducing cognitive load.

Core Features & Use Cases

File Naming: Enforces kebab-case with descriptive suffixes (e.g., .entity.ts, .use-case.ts).
Directory Naming: Guides on using plural for collections (e.g., entities/) and singular for feature modules (e.g., auth/).
Code Element Naming: Defines PascalCase for classes/interfaces, camelCase for functions/variables, and UPPER_SNAKE_CASE for constants.
Use Case: "Review my new UserService class and its associated files to ensure all names follow the project's PascalCase and kebab-case conventions, avoiding abbreviations."

Quick Start

Rename a file to follow kebab-case with a descriptive suffix, like user-profile.component.ts.

Frequently Asked Questions about naming-conventions

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

FAQPage Schema

How do I standardize naming conventions across my codebase?▼

Standardize naming conventions by applying consistent patterns: use kebab-case with descriptive suffixes for files (e.g., user-profile.entity.ts), PascalCase for classes, camelCase for functions and variables, and UPPER_SNAKE_CASE for constants. This eliminates ambiguity and improves code readability across your project.

What's the best way to name files and directories in a modular monolith?▼

Use kebab-case with semantic suffixes for files (e.g., .service.ts, .component.ts) and plural forms for collection directories (entities/, services/) while singular forms for feature modules (auth/, payment/). This structure clarifies intent and maintains consistency across bounded contexts.

Why does inconsistent naming hurt code maintainability?▼

Inconsistent naming creates confusion, increases cognitive load, and makes collaboration harder. Standardized naming conventions reduce ambiguity, make code self-documenting, and ensure all team members follow the same patterns, resulting in more maintainable and readable code.

Can I apply naming conventions during refactoring?▼

Yes. Naming conventions apply directly to refactoring scenarios—renaming classes, functions, variables, interfaces, and files to align with project standards. This ensures your refactored code maintains consistency without introducing naming drift.

Do naming conventions work for both classes and interfaces?▼

Yes. Use PascalCase for both classes and interfaces to maintain consistency. The Skill provides patterns for all code elements including files, directories, classes, interfaces, functions, and variables across your entire codebase.