type-safety

This discipline enforces type safety by disallowing 'any' types, 'as T' assertions, and '!' non-null assertions, preventing the use of 'any' to force type-checking throughout the codebase, which reduces runtime errors.

The best way to avoid 'as T' type assertions is to enforce strict type safety rules that promote safer type checks through type guards and schema parsing, preventing unsafe casting and ensuring code maintainability.

You should ban non-null '!' assertions to enforce strict type safety, encouraging optional chaining, explicit null checks, or local narrowed variables over unsafe assertions to improve code robustness and maintainability.

No, you do not need external dependencies to enforce type guards and type inference. This discipline applies to all TypeScript files in the specified paths, promoting better type checking without requiring any external packages.

You should use optional chaining instead of non-null '!' assertions whenever you need to handle potentially undefined or null values, as this enforces strict type safety and reduces the risk of runtime errors in your codebase.