accelint-ts-best-practices

You can enforce TypeScript coding standards by applying safety-first rules that require explicit return types, input validation schemas, bounded iteration, and zero-value returns to prevent runtime bugs in AI-driven code generation.

Standardize JavaScript and TypeScript code reviews by codifying rules for safe typing patterns, mutation control, DRY principles, and clear error messages, ensuring agents generate correct and maintainable code.

Progressive disclosure loads TypeScript best practices on demand, starting with one-line summaries in AGENTS.md and expanding into specific rule details from the references folder only as needed for your task.

Yes, these TypeScript safety rules apply directly to refactoring existing codebases by enforcing safe typing patterns, avoiding any and enums, preferring type aliases, and guiding controlled mutation and error handling.

Avoid any and enums in TypeScript coding practices to improve type safety and reduce runtime bugs, preferring type aliases and safe typing patterns that enforce correctness and maintainability across your codebase.

General TypeScript best practices skills do not cover performance optimization or documentation generation; they direct users to specialized skills for accelint-ts-performance and accelint-ts-documentation to handle those specific tasks.