PluginBench
Skill
Pass
Audit score 90

typescript-pro

jeffallan/claude-skills

Advanced TypeScript type systems, branded types, and tRPC end-to-end type safety for complex applications.

What is typescript-pro?

Implements advanced TypeScript patterns including custom type guards, utility types, branded types, and tRPC configuration. Use when building type-safe TypeScript applications with complex generics, conditional types, discriminated unions, or full-stack type safety requirements.

  • Design branded types and domain-driven type modeling to prevent accidental ID mix-ups
  • Create discriminated unions with exhaustive type guards for state machines and complex flows
  • Build custom utility types (DeepReadonly, RequireExactlyOne, etc.) for advanced type transformations
  • Configure strict TypeScript with optimal compiler flags and incremental compilation
  • Set up tRPC for end-to-end type safety across client and server
  • Optimize build performance with project references and declaration file generation

How to install typescript-pro

npx skills add https://github.com/jeffallan/claude-skills --skill typescript-pro
Prerequisites
  • TypeScript 5.0 or later
  • Node.js and npm/yarn for package management
Claude Code
Cursor
Windsurf
Cline

How to use typescript-pro

  1. 1.Review your current tsconfig.json and enable strict mode with recommended compiler flags
  2. 2.Identify domain entities (IDs, states) and implement branded types to prevent accidental type confusion
  3. 3.Create discriminated unions for state machines or complex conditional logic
  4. 4.Implement custom type guards using type predicates for runtime type narrowing
  5. 5.Build reusable utility types for common patterns in your codebase
  6. 6.Run `tsc --noEmit` to verify zero type errors
  7. 7.Configure tRPC routers if building full-stack applications with type-safe client-server communication
  8. 8.Validate type coverage on public APIs using type-coverage tool

Use cases

Good for
  • Building type-safe APIs with branded types to distinguish between different ID types at compile time
  • Implementing state machines using discriminated unions with exhaustive switch statements
  • Creating reusable utility types for complex domain models in monorepos
  • Configuring strict tsconfig for libraries requiring high type coverage
  • Setting up tRPC routers with full type inference from server to client
Who it's for
  • TypeScript developers building complex applications or libraries
  • Full-stack engineers implementing tRPC for end-to-end type safety
  • Teams maintaining monorepos with strict type requirements
  • Developers working on state management or domain-driven design patterns

typescript-pro FAQ

When should I use branded types instead of regular types?

Use branded types for domain modeling when you need to distinguish between semantically different values at compile time (e.g., UserId vs OrderId). They prevent accidental parameter mix-ups while maintaining runtime performance.

How do I ensure exhaustive handling of discriminated unions?

Use a default case with `const _exhaustive: never = state;` in switch statements. TypeScript will error if any union member is unhandled, ensuring all cases are covered.

What's the performance impact of strict TypeScript configuration?

Strict mode increases type-checking time but catches more errors early. Use incremental compilation and project references to optimize build performance without sacrificing type safety.

Can I use this skill without tRPC?

Yes. The skill covers advanced TypeScript patterns, branded types, and utility types independently. tRPC integration is optional for full-stack type safety.

How do I migrate existing code to use branded types?

Start with critical domain entities (IDs, tokens). Create branded type constructors and gradually replace raw types in function signatures, validating with `tsc --noEmit` after each change.

Full instructions (SKILL.md)

Source of truth, from jeffallan/claude-skills.


name: typescript-pro description: 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. license: MIT metadata: author: https://github.com/Jeffallan version: "1.1.0" domain: language triggers: TypeScript, generics, type safety, conditional types, mapped types, tRPC, tsconfig, type guards, discriminated unions role: specialist scope: implementation output-format: code related-skills: fullstack-guardian, api-designer

TypeScript Pro

Core Workflow

  1. Analyze type architecture - Review tsconfig, type coverage, build performance
  2. Design type-first APIs - Create branded types, generics, utility types
  3. Implement with type safety - Write type guards, discriminated unions, conditional types; run tsc --noEmit to catch type errors before proceeding
  4. Optimize build - Configure project references, incremental compilation, tree shaking; re-run tsc --noEmit to confirm zero errors after changes
  5. Test types - Confirm type coverage with a tool like type-coverage; validate that all public APIs have explicit return types; iterate on steps 3–4 until all checks pass

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Advanced Typesreferences/advanced-types.mdGenerics, conditional types, mapped types, template literals
Type Guardsreferences/type-guards.mdType narrowing, discriminated unions, assertion functions
Utility Typesreferences/utility-types.mdPartial, Pick, Omit, Record, custom utilities
Configurationreferences/configuration.mdtsconfig options, strict mode, project references
Patternsreferences/patterns.mdBuilder pattern, factory pattern, type-safe APIs

Code Examples

Branded Types

// Branded type for domain modeling
type Brand<T, B extends string> = T & { readonly __brand: B };
type UserId  = Brand<string, "UserId">;
type OrderId = Brand<number, "OrderId">;

const toUserId  = (id: string): UserId  => id as UserId;
const toOrderId = (id: number): OrderId => id as OrderId;

// Usage — prevents accidental id mix-ups at compile time
function getOrder(userId: UserId, orderId: OrderId) { /* ... */ }

Discriminated Unions & Type Guards

type LoadingState = { status: "loading" };
type SuccessState = { status: "success"; data: string[] };
type ErrorState   = { status: "error";   error: Error };
type RequestState = LoadingState | SuccessState | ErrorState;

// Type predicate guard
function isSuccess(state: RequestState): state is SuccessState {
  return state.status === "success";
}

// Exhaustive switch with discriminated union
function renderState(state: RequestState): string {
  switch (state.status) {
    case "loading": return "Loading…";
    case "success": return state.data.join(", ");
    case "error":   return state.error.message;
    default: {
      const _exhaustive: never = state;
      throw new Error(`Unhandled state: ${_exhaustive}`);
    }
  }
}

Custom Utility Types

// Deep readonly — immutable nested objects
type DeepReadonly<T> = {
  readonly [K in keyof T]: T[K] extends object ? DeepReadonly<T[K]> : T[K];
};

// Require exactly one of a set of keys
type RequireExactlyOne<T, Keys extends keyof T = keyof T> =
  Pick<T, Exclude<keyof T, Keys>> &
  { [K in Keys]-?: Required<Pick<T, K>> & Partial<Record<Exclude<Keys, K>, never>> }[Keys];

Recommended tsconfig.json

{
  "compilerOptions": {
    "target": "ES2022",
    "module": "NodeNext",
    "moduleResolution": "NodeNext",
    "strict": true,
    "noUncheckedIndexedAccess": true,
    "noImplicitOverride": true,
    "exactOptionalPropertyTypes": true,
    "isolatedModules": true,
    "declaration": true,
    "declarationMap": true,
    "incremental": true,
    "skipLibCheck": false
  }
}

Constraints

MUST DO

  • Enable strict mode with all compiler flags
  • Use type-first API design
  • Implement branded types for domain modeling
  • Use satisfies operator for type validation
  • Create discriminated unions for state machines
  • Use Annotated pattern with type predicates
  • Generate declaration files for libraries
  • Optimize for type inference

MUST NOT DO

  • Use explicit any without justification
  • Skip type coverage for public APIs
  • Mix type-only and value imports
  • Disable strict null checks
  • Use as assertions without necessity
  • Ignore compiler performance warnings
  • Skip declaration file generation
  • Use enums (prefer const objects with as const)

Output Templates

When implementing TypeScript features, provide:

  1. Type definitions (interfaces, types, generics)
  2. Implementation with type guards
  3. tsconfig configuration if needed
  4. Brief explanation of type design decisions

Knowledge Reference

TypeScript 5.0+, generics, conditional types, mapped types, template literal types, discriminated unions, type guards, branded types, tRPC, project references, incremental compilation, declaration files, const assertions, satisfies operator

Documentation