Scaffold a Turborepo Monorepo with Claude
Turborepo is excellent once it's set up, but the initial configuration — workspace declarations, turbo.json pipelines, shared tsconfig packages, internal package wiring — takes hours to get right from scratch. Claude does it in minutes.
Scaffold a Turborepo monorepo with:
- apps/web: Next.js 14 app
- apps/api: Fastify API
- packages/ui: shared React component library (built with tsup)
- packages/tsconfig: shared TypeScript configs
Set up turbo.json with build, test, dev, and lint pipelines.
Configure internal package dependencies so both apps can import from @repo/ui.
Claude generates the correct package.json workspace declarations, proper tsup or tsc build configs for each package, and path alias setups so TypeScript resolves internal imports correctly in both dev and production builds.
# Add a new package to an existing repo
Add a packages/email package to our existing Turborepo using React Email.
Wire up the dependency so both apps/web and apps/api can import
from @repo/email. Update turbo.json to include email in the build pipeline.
# With testing setup
Add Vitest to the monorepo with a shared config in packages/vitest-config.
Each app and package should be able to extend from @repo/vitest-config
and run tests with `turbo run test`.
Turborepo boilerplate is tedious and finicky — let Claude generate it while you focus on actual product code.
Log in to leave a comment.
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The SessionStart hook fires when any session begins or resumes, making it ideal for loading environment variables and running one-time setup scripts.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.