1---
2description: Load Turborepo skill for creating workflows, tasks, and pipelines in monorepos. Use when users ask to "create a workflow", "make a task", "generate a pipeline", or set up build orchestration.
3---
4 
5Load the Turborepo skill and help with monorepo task orchestration: creating workflows, configuring tasks, setting up pipelines, and optimizing builds.
6 
7## Workflow
8 
9### Step 1: Load turborepo skill
10 
11```
12skill({ name: 'turborepo' })
13```
14 
15### Step 2: Identify task type from user request
16 
17Analyze $ARGUMENTS to determine:
18 
19- **Topic**: configuration, caching, filtering, environment, CI, or CLI
20- **Task type**: new setup, debugging, optimization, or implementation
21 
22Use decision trees in SKILL.md to select the relevant reference files.
23 
24### Step 3: Read relevant reference files
25 
26Based on task type, read from `references/<topic>/`:
27 
28| Task                 | Files to Read                                           |
29| -------------------- | ------------------------------------------------------- |
30| Configure turbo.json | `configuration/RULE.md` + `configuration/tasks.md`      |
31| Debug cache issues   | `caching/gotchas.md`                                    |
32| Set up remote cache  | `caching/remote-cache.md`                               |
33| Filter packages      | `filtering/RULE.md` + `filtering/patterns.md`           |
34| Environment problems | `environment/gotchas.md` + `environment/modes.md`       |
35| Set up CI            | `ci/RULE.md` + `ci/github-actions.md` or `ci/vercel.md` |
36| CLI usage            | `cli/commands.md`                                       |
37 
38### Step 4: Execute task
39 
40Apply Turborepo-specific patterns from references to complete the user's request.
41 
42**CRITICAL - When creating tasks/scripts/pipelines:**
43 
441. **Prefer package tasks over Root Tasks.** Root Tasks (`//#taskname`) are only for tasks that truly cannot exist in packages, such as Vitest Projects' `//#test`, repo-wide release scripts, or tooling that does not invoke `turbo` itself.
452. Add scripts to each relevant package's `package.json` (e.g., `apps/web/package.json`, `packages/ui/package.json`)
463. Register the task in root `turbo.json`
474. Root `package.json` only contains `turbo run <task>` - never actual task logic, unless defining a valid Root Task exception
48 
49**Other things to verify:**
50 
51- `outputs` defined for cacheable tasks
52- `dependsOn` uses correct syntax (`^task` vs `task`)
53- Environment variables in `env` key
54- `.env` files in `inputs` if used
55- Use `turbo run` (not `turbo`) in package.json and CI
56 
57### Step 5: Summarize
58 
59```
60=== Turborepo Task Complete ===
61 
62Topic: <configuration|caching|filtering|environment|ci|cli>
63Files referenced: <reference files consulted>
64 
65<brief summary of what was done>
66```
67 
68<user-request>
69$ARGUMENTS
70</user-request>
71