Detect unsafe TypeScript typing and boundary-handling patterns in production code.
npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-typescript
Please help me install this Agent Skill. Skill: forge-typescript Source: https://github.com/f4rkh4d/forge-skill/tree/main/skills/backend/forge-typescript Command: npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-typescript
Prevents TypeScript codebases from silently degrading into unsafe patterns that break in production, especially through misuse of any, unchecked parsing, weak type boundaries, and missing exhaustiveness.
any, disciplined casting, and banned escape hatches: Enforces rules against any, @ts-ignore/@ts-nocheck, non-null assertions in production paths, and unprincipled as casts.Run the TypeScript discipline verifier against a file to catch forbidden patterns like any, @ts-ignore, non-null assertions, and schema-less JSON parsing.
High-intent search queries and answers about installing and using this skill.
You can enforce type safety in TypeScript by detecting unsafe typing and boundary-handling patterns. This discipline forbids `any`, bans `@ts-ignore` without linked issues, and validates external inputs using schemas before use.
The best way to validate external inputs in TypeScript is treating them as `unknown` and applying schema validation before use. This approach ensures JSON, environment variables, and API responses are safely typed at boundaries.
Exhaustive union handling for discriminated unions is achieved using an `assertNever` pattern. This ensures complete variant handling across state modeling, preventing missing cases from silently breaking production logic.
You should use Result types for expected failures and reserve exceptions for unexpected ones. This strict error-handling design pairs with a strict `tsconfig` baseline to keep TypeScript code correct and predictable.
You can eliminate `any` and unprincipled casting by enforcing rules against `as` casts and non-null assertions in production paths. A built-in verifier script flags these forbidden escape hatches automatically.
You can use the verifier on existing production code authoring and reviewing workflows. It flags common TypeScript discipline violations like missing schema validation and unsafe `any` usage to keep codebases correct.
eins78Establishes strict TypeScript patterns for tsconfig, ESLint, Zod, and typing across projects.
baseballyamaRun format, lint, type checks, tests, and builds from project manifests.
giuseppe-trisciuoglioGenerate JUnit 5 parameterized tests for boundary values and edge cases.
luyi985Model complex state logic using discriminated unions with literal tags.