Pulled ALL skills from 15 source repositories: - anthropics/skills: 16 (docs, design, MCP, testing) - obra/superpowers: 14 (TDD, debugging, agents, planning) - coreyhaines31/marketingskills: 25 (marketing, CRO, SEO, growth) - better-auth/skills: 5 (auth patterns) - vercel-labs/agent-skills: 5 (React, design, Vercel) - antfu/skills: 16 (Vue, Vite, Vitest, pnpm, Turborepo) - Plus 13 individual skills from various repos Mosaic Stack is not limited to coding — the Orchestrator and subagents serve coding, business, design, marketing, writing, logistics, analysis, and more. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
description
| description |
|---|
| 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. |
Load the Turborepo skill and help with monorepo task orchestration: creating workflows, configuring tasks, setting up pipelines, and optimizing builds.
Workflow
Step 1: Load turborepo skill
skill({ name: 'turborepo' })
Step 2: Identify task type from user request
Analyze $ARGUMENTS to determine:
- Topic: configuration, caching, filtering, environment, CI, or CLI
- Task type: new setup, debugging, optimization, or implementation
Use decision trees in SKILL.md to select the relevant reference files.
Step 3: Read relevant reference files
Based on task type, read from references/<topic>/:
| Task | Files to Read |
|---|---|
| Configure turbo.json | configuration/RULE.md + configuration/tasks.md |
| Debug cache issues | caching/gotchas.md |
| Set up remote cache | caching/remote-cache.md |
| Filter packages | filtering/RULE.md + filtering/patterns.md |
| Environment problems | environment/gotchas.md + environment/modes.md |
| Set up CI | ci/RULE.md + ci/github-actions.md or ci/vercel.md |
| CLI usage | cli/commands.md |
Step 4: Execute task
Apply Turborepo-specific patterns from references to complete the user's request.
CRITICAL - When creating tasks/scripts/pipelines:
- DO NOT create Root Tasks - Always create package tasks
- Add scripts to each relevant package's
package.json(e.g.,apps/web/package.json,packages/ui/package.json) - Register the task in root
turbo.json - Root
package.jsononly containsturbo run <task>- never actual task logic
Other things to verify:
outputsdefined for cacheable tasksdependsOnuses correct syntax (^taskvstask)- Environment variables in
envkey .envfiles ininputsif used- Use
turbo run(notturbo) in package.json and CI
Step 5: Summarize
=== Turborepo Task Complete ===
Topic: <configuration|caching|filtering|environment|ci|cli>
Files referenced: <reference files consulted>
<brief summary of what was done>