ts-rules

To enforce explicit return types and ban any in TypeScript projects, apply coding conventions that require explicit return types on exported functions and replace any with unknown paired with type guards for safer type narrowing.

The best way to handle null and undefined for safer TypeScript type checking is to prefer undefined for absence and use unknown with type guards instead of null, ensuring stricter type safety across your codebase.

Use branded types in TypeScript for strong domain modeling and safer casts, establishing strict boundaries around distinct domain values to prevent invalid assignments and improve overall code quality.

Yes, you can use these TypeScript coding standards for code reviews and linting, providing a common reference to check code quality, standardize naming, and reduce cognitive load across modules, libraries, and components.

No, this TypeScript static analysis requires no specific dependencies, allowing you to apply the coding conventions and generate a standards-compliant review checklist directly within your existing TypeScript environment.

You should use unknown instead of any for TypeScript error handling because unknown forces the use of type guards, preventing untyped leaks and preserving type-safety guarantees throughout your application logic.