What problem does it solve? TypeScript toolchain files (tsconfig.json, ESLint flat config, Prettier config) have subtle interdependencies that cause hours of debugging when misconfigured — wrong moduleResolution, broken path aliases, slow type-checking, and ESLint/Prettier rule conflicts. ## Core Features & Use Cases - Config Generation: Produces coordinated tsconfig.json, ESLint 9 flat config, .prettierrc.json, and package.json scripts for Next.js 15, Node.js/Fastify, library packages, and monorepos with project references. - Failure Diagnosis: Fixes common issues like path aliases failing at runtime, moduleResolution errors in Node.js, exactOptionalPropertyTypes breakage, and slow type-aware linting. - Use Case: A developer sets up a pnpm monorepo with a Next.js web app and Fastify API, and needs strict-mode tsconfigs, a shared ESLint flat config with Prettier conflict resolution, and VS Code integration that all work together. ## Quick Start Ask the assistant to audit and fix the TypeScript, ESLint, and Prettier configuration for your project, for example by saying "set up strict TypeScript with ESLint flat config and Prettier for my Next.js monorepo".