Skip to content

lootlog/monorepo / .agents/skills/turborepo

turborepo

Verified

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

references/ci/vercel.md

View on GitHub
# Vercel Deployment

Turborepo integrates seamlessly with Vercel for monorepo deployments.

## Remote Cache

Remote caching is **automatically enabled** when deploying to Vercel. No configuration needed - Vercel detects Turborepo and enables caching.

This means:

- No `TURBO_TOKEN` or `TURBO_TEAM` setup required on Vercel
- Cache is shared across all deployments
- Preview and production builds benefit from cache

## turbo-ignore

Skip unnecessary builds when a package hasn't changed using `turbo-ignore`.

### Installation

```bash
npx turbo-ignore
```

Or install globally in your project:

```bash
pnpm add -D turbo-ignore
```

### Setup in Vercel

1. Go to your project in Vercel Dashboard
2. Navigate to Settings > Git > Ignored Build Step
3. Select "Custom" and enter:

```bash
npx turbo-ignore
```

### How It Works

`turbo-ignore` checks if the current package (or its dependencies) changed since the last successful deployment:

1. Compares current commit to last deployed commit
2. Uses Turborepo's dependency graph
3. Returns exit code 0 (skip) if no changes
4. Returns exit code 1 (build) if changes detected

### Options

```bash
# Check specific package
npx turbo-ignore web

# Use specific comparison ref
npx turbo-ignore --fallback=HEAD~1

# Verbose output
npx turbo-ignore --verbose
```

## Environment Variables

Set environment variables in Vercel Dashboard:

1. Go to Project Settings > Environment Variables
2. Add variables for each environment (Production, Preview, Development)

Common variables:

- `DATABASE_URL`
- `API_KEY`
- Package-specific config

## Monorepo Root Directory

For monorepos, set the root directory in Vercel:

1. Project Settings > General > Root Directory
2. Set to the package path (e.g., `apps/web`)

Vercel automatically:

- Installs dependencies from monorepo root
- Runs build from the package directory
- Detects framework settings

## Build Command

Vercel auto-detects `turbo run build` when `turbo.json` exists at root.

Override if needed:

```bash
turbo run build --filter=web
```

Or for production-only optimizations:

```bash
turbo run build --filter=web --env-mode=strict
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall