naming-conventions

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.

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.

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.

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.

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.