domains / families / software-engineering / typescript-pro

typescript-pro

combined

Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety with tRPC. Master TypeScript with advanced types, generics, and strict type

When to use

• Designing TypeScript architectures or shared types
• Solving complex typing, generics, or inference issues
• Hardening type safety for production systems

When not to use

• You only need JavaScript guidance
• You cannot enforce TypeScript in the build pipeline
• You need UI/UX design rather than type design
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies overlap on the core task (advanced TypeScript typing, strict configuration, generics/utility types, and build optimization), but each contains material steps or constraints the others lack. Jeffallan/claude-skills adds a concrete 5-step workflow with tsc --noEmit and type-coverage, a reference-loading table, code examples (branded types, discriminated unions, custom utility types), a recommended tsconfig, and explicit MUST/MUST NOT constraints (e.g., no enums, use satisfies, generate declaration files). rmyndharis/antigravity-skills and sickn33/agentic-awesome-skills share a near-identical shorter instruction set (use/do-not-use, 4-step instructions, focus areas, approach, output) and add decorators/metadata, framework integration, TSDoc, and gradual typing, but lack the concrete workflow, examples, and constraints in the Jeffallan copy. Crowning one would hide the alternative approach and the extra constraints/examples, so combine is appropriate.