naming-conventions
Installation
SKILL.md
Naming Conventions
1. The Golden Rule
Code readability and predictability matter most.
Consistency Wins: If the project you are working on or the language standard contradicts the matrix below (like Python using
snake_casefor functions), always follow the existing codebase style or language idioms instead of these defaults.
2. Default Casing Matrix
Unless the codebase consistency rule overrides it, use these exact patterns:
| Casing | Used For | Examples |
|---|---|---|
camelCase |
Standard variables, local functions, methods, JSON keys. | userId, calculateTotal, isActive |
PascalCase |
Classes, Types, Interfaces, Modules, UI Components. | UserProfile, PaymentGateway, UserType |
snake_case |
Database tables, database columns, config/env keys. | user_accounts, created_at, api_key |
kebab-case |
URLs, slug parameters, file names, folders, CSS classes. | /api/v1/user-profiles, user-card.tsx, .btn-primary |
SCREAMING_SNAKE |
Global constants, immutable primitives. | MAX_RETRY_ATTEMPTS, BASE_URL |