What problem does it solve?
Teams want static type safety but dislike maintaining a compilation pipeline. This Skill configures projects so browser JavaScript gets full type checking via JSDoc annotations and Node.js executes TypeScript files natively, eliminating tsc build steps, ts-node, and tsx entirely.
Core Features & Use Cases
- JSDoc-based browser typing: Enforces pure .js files with modern @import type annotations so code runs directly in browsers while retaining IDE type checking.
- Native Node.js TypeScript execution: Configures erasableSyntaxOnly, verbatimModuleSyntax, and related tsconfig flags so Node.js v24.11.0+ runs .ts files directly without transpilation.
- Unified tsconfig guidance: Prevents anti-patterns like explicit include arrays and fragmented per-package tsconfig files in monorepos.
- Use Case: A developer starting a new ES module project asks the agent to set up type checking; the Skill produces a compliant package.json and tsconfig.json plus coding rules for both browser and Node.js code.
Quick Start
Set up type checking for my project without a build step using JSDoc for browser code and native TypeScript execution in Node.js.
