What problem does it solve? Setting up VS Code for a monorepo involves hand-writing many interlocking configuration files — .code-workspace files, launch.json debug configs, tasks.json, per-package settings, and turbo.json pipelines — and small mistakes cause broken debugging, noisy search results, or ESLint resolution failures. ## Core Features & Use Cases - Multi-root workspace generation: Produces a complete .code-workspace file with folder entries, file/watcher/search exclusions, workspace TypeScript version pinning, and recommended extensions. - Cross-package debugging: Generates launch.json configurations for Next.js, Fastify, Jest, and Prisma plus compound configs that attach to multiple apps simultaneously. - Task and pipeline automation: Creates tasks.json entries for turbo dev/build/typecheck and Prisma commands, plus a turbo.json pipeline with caching and dependency rules. - Use Case: A developer with a pnpm + Turborepo monorepo containing a Next.js web app and Fastify API asks for a VS Code setup, and receives ready-to-use workspace, debug, task, and per-package settings files adapted to their actual directory structure. ## Quick Start Ask the assistant to set up VS Code for your monorepo and share your directory structure or package.json so it can generate the workspace, launch, tasks, and turbo configuration files.
