Back to creation library
Skillv1.0.0

turborepo

Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.

All-time views0
All-time downloads1
Installs1
Views this week0
Downloads this week0
Installs this week0
Favorites2

Only events from users who opted in to optional analytics are recorded. Views are deduplicated by account, Skill, and Shanghai calendar day. Downloads are deduplicated by account, Skill, version, and Shanghai calendar day; a count means the client successfully delivered the package, not that it was saved to disk. Installs are recorded only after the client successfully writes the Skill, and are deduplicated per account and Skill for 90 days. Withdrawing consent clears personal deduplication records, so an install after opting in again may count again. “This week” means the last 7 Shanghai calendar days. Favorites show the current total.

Requested capabilities

These capabilities are declared by the publisher and reviewed again before the Skill is enabled.

0

This version does not declare any additional capabilities.

Skill steps

---
name: turborepo
description: Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
---

# Turborepo

The complete Turborepo documentation ships inside the installed `turbo` package. Do not rely on this skill for framework guidance. Always read the bundled docs, which match the installed version exactly.

Start with:

```text
node_modules/turbo/docs/README.md
```

Use that task index to choose the smallest relevant documentation page. Read it before changing Turborepo configuration, package scripts, or CI workflows.

If the package manager uses a non-flat `node_modules` layout or a workspace link, resolve the package location first:

```sh
node -p "require.resolve('turbo/package.json')"
```

Then read `docs/README.md` relative to the resolved package directory.

If `turbo` is not installed, inspect the repository's package manager and existing version constraints before adding it. After installation, use the bundled docs rather than guidance for a different release.

Version history

Published versions remain available for verification and restoration.

v1.0.0Current

Imported from vercel/turborepo@ZIP c0a37b193c3355d1e9c21377c355c6aedde261eac6c0c8998e5387a0ae6cf40d