typescript

Enforce ESM usage, strict mode, and disciplined typing in TypeScript codebases.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill typescript-dotbeeps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/typescript
Command: npx skills add https://github.com/dotBeeps/pantry --skill typescript-dotbeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript conventions help teams adopt consistent patterns (ESM usage, strict mode, and disciplined typing) to improve reliability, interoperability, and maintainability of TS codebases.

Core Features & Use Cases

  • ESM-only modules with import/export, avoiding require and module.exports
  • Type usage rules: prefer type aliases; interfaces only when needed; avoid any
  • Emphasis on strictness: enforce strict mode, readonly patterns, and modern TS features
  • Use case: migrating a TS project to standardized patterns across multiple packages

Quick Start

Configure your tsconfig for strict mode and begin refactoring code to use ESM imports with explicit types.

Frequently Asked Questions about typescript

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

FAQPage Schema
How do I enforce TypeScript strict mode and ESM conventions across a codebase?

Enforce TypeScript strict mode and ESM conventions by configuring your tsconfig for strict mode and refactoring code to use ESM imports with explicit types, ensuring type safety and maintainability across your project.

What is the best way to migrate a TypeScript project to standardized patterns?

The best way to migrate a TypeScript project to standardized patterns is through gradual refactors across files, prescribing ESM-only modules, strict mode, and disciplined typing to ensure consistency across multiple packages.

When should I use type aliases instead of interfaces in TypeScript?

You should use type aliases primarily in TypeScript, reserving interfaces only when needed. This disciplined typing approach, alongside avoiding the any type, enforces consistent typing practices for robust code.

Does this TypeScript coding standards approach work for gradual refactoring?

Yes, this TypeScript coding standards approach works for gradual refactoring by applying required patterns and compiler settings across files, ensuring type safety and maintainability without requiring a complete project overhaul.

Why should I avoid require and module.exports in TypeScript projects?

You should avoid require and module.exports in TypeScript projects to enforce ESM-only modules with import and export statements, which improves reliability, interoperability, and maintainability across TS codebases.