Enforce TypeScript type safety and naming conventions in code.
npx skills add https://github.com/alexanderguy/skills --skill typescript-alexanderguy
Please help me install this Agent Skill. Skill: typescript Source: https://github.com/alexanderguy/skills/tree/main/skills/typescript Command: npx skills add https://github.com/alexanderguy/skills --skill typescript-alexanderguy
TypeScript codebases often drift into unsafe patterns like any, brittle type assertions, non-null assertions, inconsistent naming, and unvalidated external data, which leads to bugs that only show up at runtime.
{ cause }, returning null when a request does not match a handler, and using a logger instead of console.log.Use the typescript skill to refactor a TypeScript file so it validates all external data at runtime and removes any, as, and non-null assertions while applying the repository’s naming and import conventions.
High-intent search queries and answers about installing and using this skill.
To remove unsafe TypeScript patterns, replace any and type assertions with runtime validation schemas using libraries like zod, and use type guards to safely narrow unknown types. This ensures external data is verified before use.
The best way to validate external data in TypeScript is deriving types from runtime validation schemas using libraries like zod, arktype, or typebox. This guarantees that validated fetch responses, filesystem reads, and env vars match their static types.
Structure TypeScript imports by using named exports instead of default exports, applying import type for type-only imports, and using extension-free relative imports. This import discipline prevents runtime circular dependencies and clarifies type boundaries.
Use import type in TypeScript modules to ensure types are erased at compile time and not included in the runtime bundle. This discipline avoids unnecessary runtime dependencies and clarifies which imports are strictly for type checking.
Handle errors in TypeScript by rethrowing them with a { cause } property to preserve stack traces, returning null when a request does not match a handler, and using a dedicated logger instead of console.log for structured output.
Follow TypeScript naming conventions by prefixing functions with their action like create*, is*, get*, lookup*, generate*, or handle*, applying consistent acronym casing rules for terms like URL and HTTP, and standardizing file naming across the codebase.
oborchersEnforce strict TypeScript type safety with Zod runtime validation.
angelgarciasolorzanoMonitor TypeScript code for naming conventions, import patterns, and type safety.
joyz0Validate TypeScript runtime data with TypeBox and Zod schemas.
Saurav-snapworkDetect and fix unsafe TypeScript patterns in generated TS/TSX files.