clean-typescript

The best way to avoid `any` in TypeScript is to use explicit, readable types and apply the `unknown` type appropriately when the exact shape is uncertain. This enforces type safety and reduces bugs by requiring type checking before usage.

Use `interface` vs `type` aliases in TypeScript based on your structure needs; the Skill guides you on preferring explicit definitions to enforce coding standards. Choosing correctly between them reduces cognitive load and improves maintainability.

Handle null and undefined in TypeScript functions by enforcing explicit nullability handling within your signatures. The Skill advises on explicit return types and promotes strict checks to prevent runtime errors and ensure robust API design.

You should use union types or `as const` instead of TypeScript enums to enforce cleaner type safety and avoid unexpected runtime behavior. This coding standard reduces bugs and simplifies constant usage within your codebase.

Manage error handling when refactoring JavaScript to TypeScript by explicitly typing errors and result objects. The Skill advises on explicit function signatures and avoiding unnecessary overloads to modernize legacy code and reduce cognitive load.