Instructions
When to Use
- Use for pnpm workspaces + Turborepo with Next apps.
- Prefer
github-actions-cito wire the pipelines into Actions. - Prefer
container-local-devfor Dockerized local stacks.
Structure pnpm workspaces + Turborepo for one or more Next.js apps and shared packages.
- Define
pnpm-workspace.yamlglobs; separateapps/*andpackages/*. turbo.jsonpipelines:builddepends on^build; cache outputs for Next.nextand dist folders.- Internal packages: TypeScript project references or
transpilePackagesin Next when consuming local UI libs. - Env: root vs app
.env; never duplicate secrets in git. - Versioning: single lockfile; align Node engine field.
Outcomes
- Folder tree +
turbo.jsontask outline + pnpm filter examples.
Output Rules
Commands use pnpm and turbo only; match user lockfile if mixed.
Scope and boundaries
- In scope: workspace layout, turbo pipelines, Next consumption of local packages.
- Out of scope: Nx-specific generators, Bazel.
Safety
- Read-only unless editing config files is explicitly requested.
Troubleshooting
- Module not found across workspace: check
package.jsonexportsand TypeScript paths. - Turbo cache too aggressive:
outputskeys wrong for Next - fix globs.
Related skills
github-actions-ci- workspace CI graphcontainer-local-dev- Docker for packagesdependency-migrations- coordinated bumps
GitHub: https://github.com/bh611627/skillcodex/tree/main/skills/monorepo-tooling/SKILL.md
npm: https://www.npmjs.com/package/@skillcodex/skills