---
name: "turbo-remote-cache-s3"
description: "Share build and test computation caches across developers and CI using Turborepo Remote Cache."
metadata:
  author: "Vercel"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "setup turborepo remote cache s3"
  - "configure turbo.json outputs"
  - "slash ci build time turbo"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Turborepo Remote Caching with Self-Hosted S3 / MinIO

Configures Turborepo Remote Caching: running custom remote cache servers (turborepo-remote-cache) backed by AWS S3 or MinIO, configuring turbo.json outputs and dependencies, and slashing CI times by up to 85%.

## When to Invoke
Invoke this skill whenever you need to:
- setup turborepo remote cache s3
- configure turbo.json outputs
- slash ci build time turbo

## Execution SOP & Rules
1. Define turbo.json tasks with cache: true, inputs, and outputs: ['dist/**', '.next/**'].
2. Deploy open-source ducktors/turborepo-remote-cache server configured with AWS S3 credentials.
3. In CI workflow: export TURBO_API and TURBO_TOKEN environment variables.
4. Verify remote cache hits in CI logs: '>>> FULL TURBO' indicates sub-second cached task execution.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.