Menu

Individual skill

monorepo-expert

0upvotes

Structures and scales JavaScript/TypeScript monorepos with Turborepo, Nx, and pnpm workspaces - layout rules, task pipelines, remote caching, and affected-only CI so build times stay flat as the repo grows. Use when someone asks "should we use a monorepo", "how do I set up Turborepo or Nx", "our monorepo CI takes 40 minutes", "how do I share code between apps", or "why is the cache never hitting". Do NOT use for authoring the CI workflow files themselves - use github-actions instead - and do NOT use for deciding microservice boundaries, which is about runtime architecture, not repo layout - use microservices instead.

skills/monorepo-expert/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Monorepo Expert

A monorepo's promise is shared code with atomic cross-package changes; its failure mode is CI time growing linearly with repo size until every PR waits 40 minutes to test a one-line change. The costly mistake this skill prevents is running every task on every change - the entire discipline of monorepo tooling reduces to one rule: build and test only what the diff affected, and cache everything else.

## Operating procedure

### Step 1: Gather inputs

1. Package manager and tool already in use (pnpm/npm/yarn; Turborepo/Nx/none). Default recommendation for a fresh setup: pnpm + Turborepo for simplicity, Nx when you want generators, enforced boundaries, and plugin depth.
2. Number of apps and packages, and expected growth.
3. Current CI wall-clock time and what a PR actually runs today.
4. Whether builds are reproducible - any task reading undeclared env vars or the network.
5. Team count - boundaries matter more with more teams.
Back to top