typescript-style

Enforce strict TypeScript mode, enable ESLint with type-checked rules, ban the `any` type, require explicit function return types, and use union types and discriminated unions. This prevents type-related bugs and ensures consistent typing across React components and hooks.

Use typed props interfaces, typed `useState` declarations with explicit generic parameters, and typed event handlers like `React.FormEvent`. Apply PascalCase for component names and types, camelCase for functions and variables, and `is`/`has`/`can`/`should` prefixes for boolean values.

Yes. ESLint with type-checked rules identifies common anti-patterns: implicit `any`, missing return types, loose equality (`==` vs `===`), and unhandled promises. Configure it alongside strict TypeScript mode for automated enforcement across your codebase.

Add explicit type annotations to function parameters and return types, replace `any` with concrete types or unions, use `as const` for constant objects, and apply naming conventions for booleans and types. ESLint rules help identify remaining gaps during migration.

Union types with `as const` are preferred over enums for better tree-shaking, simpler transpilation, and type inference. They provide equivalent type safety while keeping code more maintainable and reducing runtime overhead.

Keep functions concise and focused—ideally under 30 lines. Smaller functions are easier to type accurately, test, and reason about. They naturally encourage explicit return types and reduce cognitive load for type checking.