Enforce TypeScript coding standards by avoiding any and preferring specific types.
npx skills add https://github.com/bendrucker/claude --skill typescript
Please help me install this Agent Skill. Skill: typescript Source: https://github.com/bendrucker/claude/tree/main/.claude/skills/typescript Command: npx skills add https://github.com/bendrucker/claude --skill typescript
This Skill enforces strong typing and best practices in TypeScript, leading to more reliable, maintainable, and error-free codebases.
any, promoting unknown or specific types for better type inference and fewer runtime errors.// Avoid 'any' type for better type safety function processData(data: unknown): string { if (typeof data === 'string') { return data.toUpperCase(); } throw new Error('Invalid data type'); }
// Prefer specific types interface User { id: string; name: string; } const user: User = { id: '123', name: 'Alice' };
High-intent search queries and answers about installing and using this skill.
Avoiding the any type strengthens type safety by forcing explicit type declarations. Replace any with unknown when the type is uncertain, then use type guards to narrow it. For known structures, define interfaces or specific types instead. This prevents runtime errors and improves code maintainability.
Enforce type safety during code reviews by catching unsafe typing patterns like any, missing type annotations, and imprecise object types. Establish coding standards that require specific types or unknown, and use linting tools to automate detection. This reduces debugging effort and keeps the codebase reliable.
Use unknown when you receive data of uncertain type—like API responses or user input. Unknown requires explicit type checking before use, catching errors at compile time rather than runtime. This is safer than any, which bypasses type checking entirely.
Yes, type safety standards can be applied incrementally during feature development and code reviews. Start by preventing new any types in fresh code, then gradually refactor existing unsafe patterns. Linting and review practices ensure alignment with best practices across the codebase.
Precise typing catches type mismatches at compile time rather than runtime, eliminating entire categories of bugs. By defining clear interfaces and specific types, you make code intent explicit, helping developers understand data structures instantly and reducing time spent tracking down type-related issues.
JylhisAutomate TypeScript linting setup with ESLint 9 flat config.
fritzprixValidate TypeScript/React and Rust/Tauri code with linting, formatting, type checks, and builds.
HorusGoulConfigure eslint-plugin-react-render-types with flat ESLint configs in TypeScript React projects.
huialiWrite Rust const functions and const generics for compile-time computation.