What problem does it solve? Monorepo builds become slow and hard to manage as packages multiply, with redundant rebuilds, unclear task dependencies, and CI pipelines that waste time rebuilding unchanged code. This Skill provides expert guidance on Turborepo v2.8 to configure task pipelines, caching, and incremental builds correctly. ## Core Features & Use Cases - Task Pipeline Configuration: Define turbo.json task graphs with topological dependencies, outputs, inputs, and environment variable hashing. - Caching & Incremental Builds: Set up content-aware local caching, Vercel remote caching, and the --affected flag to run only changed packages and their dependents in CI. - Workspace Filtering & CI Matrices: Use filter syntax (web..., [main], !docs) and GitHub Actions matrix strategies to parallelize builds per package. - Use Case: A team with a Next.js monorepo sees CI times drop by running turbo build test lint --affected with remote caching, so only packages changed since the main branch are rebuilt and tested. ## Quick Start Ask the AI to help you configure a turbo.json pipeline with build, test, and lint tasks for your monorepo, including caching and the --affected flag for CI.