Refactor TypeScript codebases to use const-based unions and flat interfaces.
npx skills add https://github.com/sebasmzg/sebas.dot --skill typescript-sebasmzg
Please help me install this Agent Skill. Skill: typescript Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skill/typescript Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill typescript-sebasmzg
TypeScript projects often have fragile or inconsistent type definitions, duplicated runtime values, inline nested types, and unsafe uses of any; this Skill provides concise patterns and best practices to make types reliable, refactorable, and aligned with runtime values for safer and more maintainable code.
Refactor my TypeScript file to replace inline union strings with a const object extraction pattern, extract nested inline object types into named interfaces, and remove uses of any by introducing appropriate type guards and utility-type transformations.
High-intent search queries and answers about installing and using this skill.
To enforce strict TypeScript patterns, replace `any` with `unknown` and apply type guards for runtime validation. This approach ensures type safety by forcing explicit checks before accessing properties, keeping public APIs robust and predictable.
The best way to refactor nested inline object types into flat interfaces is to extract them into dedicated, named interfaces. This flat interface design improves code clarity, reusability, and extendability across domains and APIs during TypeScript migrations.
Yes, you can use utility types and `import type` annotations for library development. Applying these strict typing patterns keeps public APIs explicit, prevents runtime bundling of type-only dependencies, and ensures safer application code.
TypeScript codebases develop fragile type definitions and duplicated runtime values when types and values are managed separately. Refactoring to use const-based unions and flat interfaces aligns types with runtime values for safer, more maintainable code.
You should never use the `any` type in TypeScript code reviews when enforcing strict typing patterns. Instead of `any`, prefer `unknown` combined with type guards and utility types to maintain type safety and prevent silent runtime errors.
RevealUIStudioReplace unsafe 'any' types with unknown, generics, and type guards in TypeScript codebases.
CrisGO0510Enforce strict TypeScript patterns with const objects, flat interfaces, and type guards.
pascallammersConfigure ESLint, Prettier, and Husky to enforce coding standards.
TechyMTDerive TypeScript types from Zod schemas for runtime validation consistency.
