typescript-project-tooling

What problem does it solve? Setting up or maintaining a TypeScript repository involves many interlocking decisions—package manager, tsconfig inheritance, module resolution, linting, formatting, testing, builds, workspaces, and CI—and wrong choices create misaligned tooling that breaks builds or publishing. ## Core Features & Use Cases - Repository Inspection: Reads package.json, lockfiles, tsconfig inheritance chains, and CI configuration to determine runtime, emit strategy, and publication requirements before recommending changes. - Greenfield Setup Guidance: Selects a minimal, context-appropriate stack based on runtime, consumers, publishing, and monorepo needs rather than universal defaults. - Safe Configuration Changes: Enforces rules for target/lib derivation, module/moduleResolution pairing, project references, lockfile commits, and verified migrations. - Use Case: When adding a new package to a TypeScript monorepo, use this Skill to align its tsconfig with workspace inheritance, wire up project references, and verify build, test, and packed artifact output. ## Quick Start Review my TypeScript repository's tooling configuration and recommend improvements to the tsconfig, lint, test, and CI setup.