Naming Conventions

Universal Rules

1. English only — All code, variables, functions, files, commits, branches, PR titles: English
2. Be descriptive — getUserById not getUser, isEmailVerified not flag
3. Be consistent — Pick one term and stick with it. Don't mix user/account/member for the same concept.
4. No abbreviations — repository not repo, configuration not config. Exception: universally understood ones (id, url, api, dto, db)

By Language

Git

Project Structure

Database

API Endpoints

GET    /api/courses              ← List
GET    /api/courses/{id}         ← Get by ID
POST   /api/courses              ← Create
PUT    /api/courses/{id}         ← Full update
PATCH  /api/courses/{id}         ← Partial update
DELETE /api/courses/{id}         ← Delete

# Nested resources
GET    /api/courses/{id}/students
POST   /api/courses/{id}/enroll

• Plural nouns for resources
• kebab-case for multi-word: /api/course-categories
• No verbs in URLs (except actions): /api/courses/{id}/enroll is OK
• Version prefix if needed: /api/v1/courses

Common Naming Patterns