Enforce naming standards

Naming standards in code serve as a universal language that communicates purpose and functionality across development teams. Consistent naming patterns make code more predictable and maintainable by clearly indicating the role and type of each component. When names follow established conventions, such as PascalCase for interfaces and camelCase for functions, they create patterns that both humans and AI systems can reliably interpret. This consistency is particularly valuable for AI tools, which rely on these patterns to understand code structure and generate appropriate suggestions.

Examples

• Variables (camelCase): firstName, maxRetryAttempts, isUserLoggedIn
• Classes (PascalCase): PaymentProcessor, EventEmitter, FileUploader
• Methods/Functions (camelCase): calculateTotal, validateUserInput
• Constants (SCREAMING_SNAKE_CASE): MYSQL_PORT, API_BASE_URL,
• File Names (kebab-case): user-service.ts, event-handler.cpp

Recommendation

Implement a comprehensive naming convention that covers all code elements, from variables to file structures. For example, use PascalCase for classes and interfaces, camelCase for functions and variables, and kebab-case for files and directories. Prefix interfaces with 'I' and types with 'T'. Ensure names are descriptive and reflect their purpose, avoiding abbreviations unless widely recognized. Document these standards in a style guide and enforce them through automated linting tools to maintain consistency across the codebase.