Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance in monorepos
The turborepo-monorepo skill provides comprehensive guidance for managing Turborepo monorepos in TypeScript/JavaScript projects. It addresses the complexity of coordinating builds, tests, and CI across many packages by codifying how to structure workspaces, configure task pipelines, and optimize build performance and caching.
The skill covers workspace creation (via `create turbo` or adding turbo to an existing project), authoring `turbo.json` task definitions with `dependsOn`, `outputs`, and inputs, and validating the task graph with `--dry-run` before CI. It documents framework integration for Next.js (`.next/**` outputs, `NEXT_PUBLIC_*` env) and NestJS (persistent, non-cached dev tasks), testing pipelines for Vitest and Jest including running only affected packages with `--filter=[HEAD^]`, and package-level config extension patterns. Bundled reference files provide complete CI/CD workflows for GitHub Actions, GitLab CI, and CircleCI, remote caching with Vercel Remote Cache (using TURBO_TOKEN/TURBO_TEAM secrets), artifact caching, turbo-ignore for skipping unnecessary builds, and a multi-stage Docker build example.
Target users are frontend and full-stack TypeScript/JavaScript developers and platform engineers building or maintaining monorepos, setting up CI/CD, or migrating from other monorepo tools. Typical use cases include initializing workspaces, tuning cache hit ratios, debugging task-dependency issues, and standardizing pipeline configuration across teams. The commands it uses are standard package-manager, turbo, and CI operations, and remote-cache credentials are referenced through CI secret variables rather than being hardcoded.
Examples use pnpm and cover Next.js and NestJS apps, along with Vitest/Jest test pipelines, though the turbo.json patterns apply generally to TypeScript/JavaScript monorepos.
Use turbo/pnpm filters such as --filter=[HEAD^] to lint, test, and build only affected packages, and validate the task graph with --dry-run before CI to confirm the expected packages run.
The reference files include complete workflows for GitHub Actions, GitLab CI, and CircleCI, plus a multi-stage Dockerfile and deployment pipeline examples.
Remote caching uses Vercel Remote Cache with TURBO_TOKEN and TURBO_TEAM supplied as CI secret/environment variables rather than being committed, with a local cache fallback if remote cache is unavailable.
Yes. Migrating from other monorepo tools to Turborepo is listed among its when-to-use scenarios, alongside debugging task-dependency and cache issues.
Quick Setup:
.claude/skills/Repository
giuseppe-trisciuoglio/developer-kit