TU

Guides developers in setting up efficient Turborepo monorepo build systems, caching, and task pipelines.

Install

mkdir -p .claude/skills/turborepo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/519" && unzip -o skill.zip -d .claude/skills/turborepo && rm skill.zip

Installs to .claude/skills/turborepo

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
461 chars · catalog description✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Isolate build logic into individual packages
  • →Register task dependency graphs in turbo.json
  • →Configure remote cache for CI/CD environments
  • →Delegate root execution to package scripts

How it works

It enforces a dependency graph execution model by separating task definitions in workspace packages from the root orchestrator, enabling parallel processing and persistent caching.

Inputs & outputs

You give it
Monorepo task requirements and package structure
You get back
Optimized turbo.json configuration and package.json scripts

When to use turborepo

  • →Configure task pipelines for monorepos
  • →Debug remote caching issues
  • →Optimize CI/CD build performance
  • →Set up internal package boundaries

About this skill

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:

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:

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.

When not to use it

  • →Single-repository projects with no sub-packages
  • →Small projects where build parallelization adds overhead

Prerequisites

Turbo CLI installed globally or in devDependencies

Limitations

  • →Requires strict monorepo directory standards
  • →Adds configuration complexity for small teams

How it compares

It forces decentralization of build logic, ensuring that tasks are tied to specific packages rather than global root scripts.

Compared to similar skills

turborepo side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
turborepo (this skill)613moReviewIntermediate
upgrading-expo35moReviewIntermediate
pnpm-upgrade25moReviewIntermediate
pnpm08moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

web-design-guidelines

vercel

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

3290

update-docs

vercel

This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.

2543

streamdown

vercel

Implement, configure, and customize Streamdown — a streaming-optimized React Markdown renderer with syntax highlighting, Mermaid diagrams, math rendering, and CJK support. Use when working with Streamdown setup, configuration, plugins, styling, security, or integration with AI streaming (e.g., Vercel AI SDK). Triggers on: (1) Installing or setting up Streamdown, (2) Configuring plugins (code, mermaid, math, cjk), (3) Styling or theming Streamdown output, (4) Integrating with AI chat/streaming, (5) Configuring security, link safety, or custom HTML tags, (6) Using carets, static mode, or custom components, (7) Troubleshooting Tailwind, Shiki, or Vite issues.

1236

ai-sdk

vercel

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

1150

list-npm-package-content

vercel

List the contents of an npm package tarball before publishing. Use when the user wants to see what files are included in an npm bundle, verify package contents, or debug npm publish issues.

632

develop-ai-functions-example

vercel

Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures.

536

Search skills

Search the agent skills registry