Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use for scoped monorepo setup, build or dependency review.
Start a fresh conversation. Replace the highlighted placeholders.
Use monorepo-architect to propose a scalable monorepo architecture for [projects], using [build system preference] and [team constraints], with dependency-boundary and caching recommendations.
Required inputs
[projects]
[build system preference]
[team constraints]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: monorepo-architectdescription: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use for scoped monorepo setup, build or dependency review."risk: safesource: communitydate_added: "2026-02-27"
Monorepo Architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use for scoped monorepo setup, build or dependency review. build optimization, or scaling development workflows across teams.
Do not use this skill when
The task is unrelated to monorepo architect
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Use remote caching only when authorized and justified; review private artifact/credential transmission and cross-tenant cache integrity
Keep shared libraries focused
Use tags for dependency constraints
Automate dependency updates
Document the dependency graph
Set up code ownership rules
Example
User request:
Set up a new monorepo from scratch.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Preserve the existing build/package manager unless migration is requested. Verify cache keys cover sources, lockfiles, tools and relevant environment; never cache secrets. Check affected-build detection against a full build for cross-project changes before trusting it to omit required checks.