typescript-and-javascript

To enforce strict type safety in TypeScript, you must prohibit the use of 'any', mandate strict equality operators like '===' and '!==', and prefer traceable typing using the 'satisfies' operator over type casting. This approach ensures predictable code and prevents unsafe typing errors.

Improving tree-shaking in JavaScript involves discouraging barrel exports and preventing accidental logic in entry-point files like 'index.ts'. By organizing code this way, you reduce side effects and ensure that unused modules are safely eliminated during the bundling process.

You should use 'satisfies' instead of type casting in TypeScript because it provides traceability and validates that an object matches a type without losing its specific literal types. This prevents unsafe type assertions and maintains strict type-checking expectations.

To format readable control-flow patterns in TypeScript, use early returns, prefer named functions over arrow functions where appropriate, and consistently apply curly braces. This creates predictable control flow and ensures the generated code remains maintainable.

Yes, this strict TypeScript style guide applies to configuration files, tests, scripts, components, hooks, services, utilities, classes, interfaces, types, and schemas. It enforces style and type-safety policies across all TS/JS file operations and agent-authored content.