Type Safety Guardian

To enforce strict TypeScript typing during code review, apply zero-tolerance rules that detect forbidden weak-typing constructs like `any` and unsafe `unknown`, requiring explicit public method return types and safe alternatives such as discriminated unions.

Refactoring TypeScript code to satisfy ADR-0006 involves rejecting `any` and `unknown` misuse, enforcing explicit return types on public methods, and promoting strong typing patterns like discriminated unions and shared core types to ensure production readiness.

Prevent type drift and `any` regressions during third-party integration by detecting forbidden weak-typing patterns and guiding you to strictly typed equivalents, ensuring that external dependencies do not compromise your internal type safety.

TypeScript builds fail when unsafe `unknown` types violate strict typing rules, requiring you to replace them with safe type patterns through a structured remediation workflow that flags violations, explains root causes, and pushes correctly typed solutions.

Yes, you can block `any` types by applying strict typing rules that detect and reject forbidden weak-typing constructs, enforce explicit return types on public methods, and guide replacements with compliant alternatives like discriminated unions.