mcpField
T
typescript-advanced

typescript-advanced

github.com/marcioaltoeDevelopment063 installsUpdated today
Repository

About typescript-advanced

A TypeScript skill for developers working with advanced types, including inference and reusable utilities. It emphasizes simple contracts and repository conventions.

Key features

  1. 01Generics, conditional, and mapped types
  2. 02Template literals and utility types
  3. 03Inference and narrowing
  4. 04Compile-time contract tests
  5. 05Compiler and complexity guidance

Use cases

  1. 01Building reusable type utilities
  2. 02Debugging generic inference
  3. 03Testing type contracts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/marcioaltoe/skills --skill typescript-advanced

After installing, type/typescript-advancedin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
advanced-patterns.md
best-practices.md
core-concepts.md
type-inference.md

Details

From the project README

TypeScript Advanced Types

Use this skill when generic inference, conditional/mapped types, template literals, or a reusable type utility is the actual problem. Ordinary typed API, form, and state work uses its domain guidance unless advanced type behavior needs attention.

Concern being changedReference
Generics, conditional/mapped/template-literal and utility typesreferences/core-concepts.md
Reusable emitters, builders, clients, deep utilities, or discriminated modelsreferences/advanced-patterns.md
infer, narrowing, assertion functions, and type-contract testsreferences/type-inference.md
Compiler configuration, type complexity, and maintainabilityreferences/best-practices.md

Prefer the simplest type that expresses the contract. Use unknown and real narrowing at untrusted boundaries; preserve discriminants and readonly intent. Let inference handle local values and follow repository conventions for public annotations, interface, and type.

Use the existing tsconfig; reference configurations are examples, not instructions to change it. Add compile-time tests only when type behavior is a product/library contract, using its owning suite. Avoid a new type framework or elaborate generic abstraction for a single ordinary call site. Run the repository's affected typecheck gate.

Comments

Markdown supported