Turborepo

Turborepo is a skill from Vercel’s official Turborepo repository. According to the provider, it explains how an agent can analyze, structure, and operate JavaScript and TypeScript monorepos with the Turborepo build system. The skill is not a build platform of its own, not a hosting account, and not a replacement for the Turborepo CLI. It provides guidance for turbo.json, tasks, dependencies, cached outputs, environment variables, filters, affected packages, CI, and package boundaries. The project team remains responsible for source code, toolchains, runners, and approvals.

Package-owned tasks

The primary source’s central recommendation is to define tasks as scripts in the packages that own them. Applications and libraries describe their own build, test, and lint scripts, while the root configuration orchestrates those tasks through Turborepo. This keeps responsibility close to the code and lets the dependency graph schedule independent work in parallel. Root tasks are reserved for repository-wide work that genuinely belongs nowhere else. The skill helps identify that boundary and discourages root scripts that bypass the package structure through manual directory changes or chained individual commands.

Graph, cache, and configuration

The guidance places dependsOn, outputs, inputs, env, and persistent development tasks in the task graph. Dependencies between packages should be visible in workspace metadata so a configuration using ^build can establish the correct order. Outputs must be described when they should be restored reliably. Relevant environment variables and dotenv files must participate in hash inputs, otherwise stale results may be treated as valid. For tasks that can run in parallel but whose cache must still be invalidated by dependency changes, the source describes transit nodes as a clean pattern. Cache hits are an optimization mechanism, not proof that a result is functionally correct.

Filters, CI, and development

For large monorepos, the skill explains selection by package name, path, dependencies, and changes. According to the provider, affected is the preferred way to determine changed packages and their dependents; a different comparison base is explicitly configured through the relevant environment variable. In CI, scripts should use the explicit turbo run form, while the shorter form is intended for individual interactive terminal invocations. For development sessions, the source covers turbo watch, persistent processes, development-task dependencies, and interruptible tasks. These recommendations do not replace inspection of the actual CI system, shell, package-manager configuration, or Turborepo version in use.

Boundaries, security, and professional context

The skill does not automatically read or change a repository and does not grant permissions. During a concrete execution, however, an agent may process files, build artifacts, logs, or CI configuration. Tokens, credentials, and private environment values must not be placed in skill text, prompts, commit history, or logs. Remote caching and CI can transmit source information, metadata, or artifacts to additional systems; retention, access, region, and provider terms should be reviewed before use. A local build does not automatically make data confidential if a selected agent or model provider processes the content. Official Vercel and Turborepo documentation remains authoritative for current configuration details. The repository identifies the MIT license. Current terms should be checked directly with the provider; this entry states no concrete prices.