monorepo
Original:🇺🇸 English
Translated
Monorepo architecture patterns with Turborepo, pnpm workspaces, and shared packages. Use when setting up multi-package repositories, shared libraries, or micro-frontend architectures.
5installs
Sourcealicoder001/agent-skills
Added on
NPX Install
npx skill4agent add alicoder001/agent-skills monorepoTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Monorepo Architecture
Use this skill to create predictable package boundaries, shared tooling, and fast incremental builds.
Use This Skill When
- Multiple apps share code and release cadence.
- You need shared packages (,
ui,types,config).utils - Build/test/lint pipelines need workspace-level orchestration.
Core Contract
- Keep deployable apps in .
apps/ - Keep reusable packages in .
packages/ - Use workspace protocol dependencies ().
workspace:* - Use Turbo pipelines for dependency-aware task execution.
- Keep environment variables explicit per app/package boundary.
Recommended Structure
text
apps/
packages/
turbo.json
pnpm-workspace.yaml
package.jsonImplementation Workflow
1) Workspace Setup
- Configure .
pnpm-workspace.yaml - Define root scripts for ,
dev,build,lint.test - Add Turbo pipeline with and
dependsOn.outputs
2) Shared Packages
- Create ,
packages/ui,packages/types.packages/config - Export public APIs from package roots.
- Keep package boundaries strict and testable.
3) App Integration
- Consume shared packages via workspace deps.
- Keep app-specific runtime config local to app.
- Avoid hidden coupling through root-only env assumptions.
4) Operational Quality
- Cache-friendly tasks and deterministic outputs.
- Per-package ownership and CI filters.
- Versioning/release strategy documented.
Output Requirements for Agent
- Folder layout proposal.
- Workspace and Turbo config.
- Shared package strategy.
- CI/build command matrix.
References
- Detailed setup files and command examples:
references/guide.md