Naming conventions are consistent

Mixed naming conventions — camelCase functions next to snake_case utilities, PascalCase components alongside kebab-case file names — slow down code review, create false matches during search, and generate typo-based import errors that TypeScript only catches if the module resolution fails. ISO 25010 maintainability.analysability degrades because developers cannot predict where code lives or what it's called. AI-generated projects are especially prone to this: convention drift accumulates across sessions as the model applies whatever convention seems locally natural.

Codify the convention in ESLint so violations are flagged automatically:

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

Run eslint --fix across the codebase to catch and flag existing violations. For file names, use a consistent casing convention and enforce it in CI with a filename linter.