typescript

To enforce type safety in TypeScript, you must avoid the any type and prefer using unknown or generics. This preserves static typing rules and enables safer type guards during code refactoring.

The best way to define a single source of truth is using the const objects pattern. You create a const object and derive a type from its values using the as const pattern to prevent fragile unions.

You structure flat interfaces by defining one-level deep interfaces for simple, reusable shapes. This avoids inlining nested structures and maintains maintainable type declarations across your project.

You should use utility types like Pick, Omit, Partial, and Required during refactoring to compose adaptable shapes. They allow you to modify existing interfaces without duplicating type declarations.

Yes, you can implement type guards to narrow unknown values safely and use type-only imports when appropriate. This approach ensures explicit imports and preserves strict static typing rules.

Yes, this approach works for feature work and code reviews by targeting TypeScript projects during refactoring. It focuses on type declarations, interfaces, generics, and const patterns to ensure safer code.