typescript

To enforce strict type-safety in TypeScript, apply patterns that discourage `any` and promote `unknown` alongside safe generics. This approach handles uncertain data reliably and prevents runtime errors during codebase refactoring.

The best way to structure flat TypeScript interfaces for maintainability is to enforce explicit typing and const-based patterns. Deriving runtime values from stable sources improves readability and scalability across the codebase.

To apply type guards and utility types when refactoring .ts and .tsx files, follow strict TypeScript patterns that provide guidance for common type-safety scenarios. This ensures reliable application of utility types and overall codebase maintainability.

Yes, this TypeScript refactoring approach works for onboarding teams to best practices. It audits projects and applies strict patterns to satisfy requirements for const-based usage, flat interfaces, and Import Types, improving team consistency.

You should use `unknown` instead of `any` to handle uncertain data in TypeScript when you need strict type-safety. Promoting `unknown` and safe generics discourages weak type guarantees and prevents inconsistent patterns that lead to runtime errors.