writing-effective-typescript

Apply 83 decision criteria to TypeScript type-system design choices.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/sumik5/sumik-claude-plugin --skill writing-effective-typescript
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-effective-typescript
Source: https://github.com/sumik5/sumik-claude-plugin/tree/main/skills/writing-effective-typescript
Command: npx skills add https://github.com/sumik5/sumik-claude-plugin --skill writing-effective-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge base provides a comprehensive set of TypeScript best-practice decision criteria, helping engineers decide how to structure types, apply generics, and reason about inference and soundness in real-world code.

Core Features & Use Cases

  • 83 decision criteria covering type-system design, inference patterns, generics, and soundness trade-offs.
  • Guidance for common scenarios such as interface vs type, readonly contracts, and type-level vs value-level concerns during design, refactor, and migration.
  • Cross-references to related skills for deeper references: mastering-typescript for language feature usage and enforcing-type-safety for strict rules.

Quick Start

Provide a TypeScript design decision by applying the 83 criteria to guide the chosen approach.

Frequently Asked Questions about writing-effective-typescript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to decide between using an interface or a type alias in TypeScript?▼

For TypeScript design choices between interface and type, this framework provides decision criteria evaluating type-system structure, readonly contracts, and soundness trade-offs to ensure consistent, maintainable code.

How do I apply generics safely during a TypeScript code refactor?▼

To apply generics safely during a TypeScript refactor, use the 83 decision guidelines covering inference patterns and type-level versus value-level concerns to maintain type safety and structural consistency.

When do I need strict type inference rules for TypeScript migrations?▼

You need strict type inference rules for TypeScript migrations when type-system choices impact maintainability, requiring precise decision criteria to evaluate safety trade-offs and structural soundness across the codebase.

Does this TypeScript best-practices framework cover type-level and value-level design trade-offs?▼

Yes, the TypeScript best-practices framework covers type-level and value-level design trade-offs, offering specific criteria to evaluate inference patterns, generics, and readonly contracts during design and code reviews.

What are the limitations of relying on type inference for TypeScript safety?▼

Limitations of TypeScript type inference involve soundness trade-offs where automated inference may not guarantee structural safety, requiring explicit design criteria to evaluate when to enforce strict type rules.