type-safety

Fix @typescript-eslint/no-unsafe-* errors by implementing type guards and runtime validation patterns to replace unsafe any and unknown usage. This skill detects unsafe member access, assignments, and returns, generating guards to enforce strict static analysis.

Enforce TypeScript type safety by applying centralized workflows that generate type guards and validate data. This approach surfaces unsafe patterns like any usage and provides explicit runtime validation to prevent errors during code modification and refactoring.

Yes, you can automatically generate type guards for unknown variables in TypeScript. This skill includes detection scripts to surface unsafe operations and generators to produce runtime guards, aligning with workflows for member-access and argument safety.

Yes, this static analysis approach works for runtime validation by generating type guards that bridge compile-time checks and runtime safety. It remediates unsafe calls and arguments, ensuring data validated at runtime matches the expected TypeScript typings.

You need runtime type guards because static analysis cannot prevent runtime risks caused by unguarded operations and any usage. Implementing validation patterns ensures data integrity at boundaries, improving maintainability and preventing errors that TypeScript alone misses.