
Typescript Strict Mode Enforcer
Transform TypeScript codebases to enforce strict mode type safety
What You Can Do
This skill scans your TypeScript codebase for type safety violations and systematically remediates them. You can automatically remove implicit any types, add comprehensive type annotations to functions and variables, configure strict mode compiler options in tsconfig.json, and receive actionable refactoring guidance with concrete code examples. It's designed for migrating existing projects to strict mode or enforcing strict practices before production deployment.
Features
Identifies implicit `any` types, missing annotations, and unsafe patterns
Replaces unsafe `any` usage with proper inferred or explicit types
Adds complete type signatures to parameters, return types, and variable declarations
Validates and updates compiler options for strict mode, strictNullChecks, noImplicitAny, and related settings
Scans entire codebase to ensure consistent type coverage and safety
Provides specific code examples and before/after transformations for implementation
Ensures third-party type definitions integrate properly without type gaps
Example Output
Example 1: Implicit any Detection and Fix
// Before
function processData(input) {
return input.value;
}
// After
function processData(input: { value: string }): string {
return input.value;
}
Example 2: tsconfig.json Strict Mode Configuration
{
"compilerOptions": {
"strict": true,
"strictNullChecks": true,
"strictFunctionTypes": true,
"noImplicitAny": true,
"noImplicitThis": true
}
}
Example 3: Type Safety Report
Violations found: 23 implicit any types, 15 unannotated parameters, 8 unsafe null access patterns. Refactoring recommendations with code samples for each category.
What's Included
- SKILL.md instruction file with detailed configuration guidelines:
- TypeScript strict mode configuration template:
- Type safety violation checklist:
- tsconfig.json reference with compiler option explanations:
- Before/after refactoring examples for common patterns:
Who It's For
- Backend TypeScript engineers migrating projects to strict mode
- Full-stack developers hardening type safety in production codebases
- Tech leads enforcing code quality standards across teams
- DevOps engineers automating type safety validation in CI/CD pipelines
- Software architects planning type-safe architecture transitions
Best For
- Migrating existing TypeScript projects to strict mode for the first time
- Refactoring legacy codebases with widespread `any` type usage
- Pre-production type safety hardening and validation
- Enforcing team-wide strict mode standards during onboarding
- Eliminating type-related runtime errors in critical application paths






