naming-conventions

Name: naming-conventions
Availability: InStock
Author: willyu1007

Enforce kebab-case naming conventions for directories, files, and identifiers.

Updated Dec 22, 2025

Search Tags:#code organization #developer productivity #naming conventions #code standards #kebab-case #ssot

Ready to run

npx skills add https://github.com/willyu1007/Template-Skill-Basic --skill naming-conventions-willyu1007

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: naming-conventions
Source: https://github.com/willyu1007/Template-Skill-Basic/tree/main/.claude/skills/standards/naming-conventions
Command: npx skills add https://github.com/willyu1007/Template-Skill-Basic --skill naming-conventions-willyu1007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that all code artifacts, including directories, files, and identifiers, adhere to a consistent and predictable naming convention, reducing confusion and improving maintainability.

Core Features & Use Cases

Kebab-Case Enforcement: Standardizes naming to kebab-case for directories and files.
SSOT Layout Guidance: Provides rules for organizing files within the Single Source of Truth structure.
Skill Naming Standards: Defines conventions for naming individual skills.
Script-Generated File Paths: Manages naming for temporary and generated files, including those in .ai/.tmp/.
Use Case: When creating a new feature, this skill helps ensure all related files and directories are named according to the established project standards, making the codebase easier to navigate for all team members.

Quick Start

Apply the naming conventions skill to ensure the new file 'my-new-feature.py' follows the project's standards.

Frequently Asked Questions about naming-conventions

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

FAQPage Schema

How do I enforce kebab-case naming conventions for files and directories?▼

To enforce kebab-case naming, standardize all directory and file names to use lowercase letters separated by hyphens. This approach ensures codebase consistency, reducing confusion and improving maintainability for all team members.

What is the best way to organize files within a Single Source of Truth structure?▼

Organizing files within a Single Source of Truth structure requires specific layout guidance that standardizes where code artifacts live. This standardization supports developer onboarding and codebase navigation by providing a predictable directory structure.

How do I standardize naming for script-generated and temporary file paths?▼

Standardize script-generated file paths by applying naming conventions to temporary files, including those in `.ai/.tmp/` directories. This ensures even automated and transient code artifacts adhere to project standards and maintain consistency.

Does this naming standardization approach work for developer onboarding?▼

Yes, standardizing code structure supports developer onboarding by making the codebase easier to navigate. When all directories, files, and identifiers adhere to predictable kebab-case rules, new team members can locate and understand code artifacts faster.

Why should I use kebab-case for code organization instead of other naming styles?▼

Using kebab-case for code organization provides a consistent and predictable naming convention across directories and files. This standardization reduces confusion when navigating the codebase and ensures all related files follow established project standards.

Can I define skill naming standards alongside regular file naming conventions?▼

Yes, you can define skill naming standards alongside standard file and directory naming conventions. This ensures all individual skills and their related code artifacts adhere to the same kebab-case rules and SSOT layout guidance.