Naming conventions consistent

Inconsistent naming conventions in TypeScript code — snake_case variables, Hungarian notation, mixed component casing — increase cognitive load for every developer reading the code and signal that the project lacks enforced standards. ISO 25010:2011 §6.5.2 classifies this as a readability and maintainability defect. In practice, mixed conventions also correlate with inconsistent module structure, inconsistent error handling, and higher defect rates: they are a proxy signal for how rigorously the codebase enforces its own standards.

Define a convention and enforce it with ESLint's @typescript-eslint/naming-convention rule so violations are caught automatically:

{
  "rules": {
    "@typescript-eslint/naming-convention": [
      "error",
      { "selector": "variable", "format": ["camelCase", "UPPER_CASE"] },
      { "selector": "function", "format": ["camelCase", "PascalCase"] },
      { "selector": "typeLike", "format": ["PascalCase"] },
      { "selector": "interface", "format": ["PascalCase"] }
    ]
  }
}

For existing violations, use eslint --fix for auto-fixable cases. Snake_case variables in TypeScript code (user_id, is_valid) are the most common — run a search-replace pass on the highest-traffic files first.