What problem does it solve? Monorepo builds become slow and wasteful when every task re-runs on every change, and teams struggle to configure Turborepo pipelines, cache keys, and remote caching correctly across local development and CI. ## Core Features & Use Cases - Pipeline Configuration: Ready-to-use turbo.json templates covering build, test, lint, typecheck, dev, and deploy tasks with proper dependsOn, inputs, outputs, and env declarations. - Remote Caching Setup: Instructions for Vercel remote caching (TURBO_TOKEN/TURBO_TEAM) plus a self-hosted Express cache server implementing the Turborepo artifacts API. - Filtering and CI Integration: Filter syntax for building only affected packages and a GitHub Actions workflow that builds and tests only what changed since origin/main. - Use Case: A team migrating to a monorepo uses the templates to define their pipeline, enable remote caching in CI, and debug cache misses with dry-run and verbosity flags. ## Quick Start Ask the AI to set up a turbo.json pipeline with remote caching and a CI workflow that only builds packages changed since the main branch.