typescript

Type safety in code reviews is enforced through strict interfaces, generics, and null-safety guidelines. This Skill provides standardized practices for TypeScript that establish clear type contracts, making it easier to catch type-related issues during review and ensure consistent typing discipline across your codebase.

TypeScript coding standards cover strict interfaces, generics patterns, null-safety practices, and build-tool compatibility. Following these guidelines improves maintainability by creating consistent, type-safe code that's easier for teams to understand, review, and refactor across .ts, .tsx, and .mts files.

Yes. Standardized TypeScript practices provide new contributors with a shared baseline for code style and type safety, enabling them to align quickly with project conventions. This reduces onboarding friction and ensures consistent quality from the start.

Apply standardized TypeScript guidelines to refactoring work by enforcing strict types, proper generics usage, and null-safety patterns. This approach improves code quality and maintainability while ensuring consistent type discipline across your project.

Best practices for generics involve clear, reusable type contracts that avoid unnecessary complexity. Null-safety is achieved through strict type annotations and defensive patterns. Together, these practices reduce runtime errors and create more predictable, maintainable TypeScript code.

Yes. TypeScript coding standards and linting apply across all TypeScript file types—.ts, .tsx, and .mts—ensuring consistent type practices and code style regardless of whether you're working with component files or module variations.