What problem does it solve? Setting up VS Code for a monorepo involves tedious, error-prone configuration across many files: multi-root workspace definitions, per-package settings, cross-package debug configs, and task runners. This Skill generates complete, copyable configuration files so developers stop fighting Explorer noise, broken ESLint resolution, and single-package debugging. ## Core Features & Use Cases - Multi-root workspace generation: Produces a .code-workspace file with folder mappings, file/watcher/search exclusions, workspace TypeScript version pinning, and recommended extensions. - Cross-package debugging: Generates launch.json with per-app debug configurations (Next.js, Fastify, Jest, Prisma) plus compound configs to debug web and API simultaneously. - Task and pipeline automation: Creates tasks.json for turbo dev/build/typecheck and Prisma commands, plus a turbo.json pipeline with caching and dependency rules. - Use Case: A developer joins a pnpm + Turborepo project with a Next.js frontend and Fastify API. They ask to set up VS Code, and receive a complete .code-workspace, launch.json with a full-stack debug compound, tasks.json, and per-package settings — all immediately usable. ## Quick Start Ask the assistant to set up VS Code for your monorepo, sharing your directory structure or package.json so it can generate the workspace, debug, and task configuration files.