typescript-guidelines

To enforce strict TypeScript mode, enable strict flags in tsconfig and prohibit `any` alongside unchecked type assertions. This discipline prevents unsafe patterns during code generation, reviews, and refactoring while improving overall type safety.

Schema-first TypeScript uses schemas to parse and validate data at trust boundaries, guaranteeing runtime type safety. You need this approach when crossing frontend and backend boundaries to verify untrusted data shapes before application consumption.

You audit tsconfig for type-safety by verifying strict mode is enabled and checking for configurations that allow unsafe patterns. Apply these rules during refactoring to enforce consistent type discipline and safer boundaries across existing projects.

Yes, you can apply strict TypeScript guidelines across both frontend and backend projects. The rules enforce type discipline universally, requiring strict mode and schema-first boundaries to improve maintainability and prevent runtime errors everywhere.

You should avoid `any` in TypeScript because it bypasses compiler type checking, leading to potential runtime errors. Unchecked type assertions are limited because they override the compiler without validation, creating unsafe patterns that reduce maintainability.

The best way to prevent runtime errors during TypeScript refactoring is to run in strict mode, prohibit `any`, and use schema-first parsing at trust boundaries. This enforces consistent type discipline and validates untrusted data shapes before use.