Architect Monorepos for Scalable Development
Sets up and scales monorepo architecture: tool selection (Nx, Turborepo, Bazel, Lerna), build caching, and CI optimization.
Why it matters
Optimize your development workflow by architecting efficient monorepos. This skill leverages expert knowledge of tools like Nx, Turborepo, Bazel, and Lerna to streamline build processes, manage dependencies, and scale code sharing across teams.
Outcomes
What it gets done
Select and configure optimal monorepo tooling (Nx, Turborepo, Bazel, Lerna)
Design workspace structure and optimize build caching
Implement dependency management and affected/changed detection for CI
Facilitate code sharing and task orchestration across multiple projects
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-monorepo-architect | bash Overview
Monorepo Architect
Provides expert guidance on monorepo architecture covering tool selection, workspace configuration, build caching, and CI optimization across Nx, Turborepo, Bazel, and Lerna. Use when setting up a new monorepo, migrating from polyrepo, or optimizing slow CI/CD pipelines.
What it does
Provides expert guidance on monorepo architecture, build systems, and dependency management at scale - covering tool selection, workspace configuration, build caching, and task orchestration across Nx, Turborepo, Bazel, and Lerna.
When to use - and when NOT to
Use this skill when setting up a new monorepo from scratch, migrating from polyrepo to monorepo, optimizing slow CI/CD pipelines, sharing code between multiple applications, managing dependencies across projects, or implementing consistent tooling across teams. Not a fit for single-project repositories with no code-sharing or multi-team scaling needs.
Inputs and outputs
Covers monorepo tool selection across Nx, Turborepo, Bazel, and Lerna, workspace configuration and project structure design, build caching (both local and remote), dependency graph management, affected/changed detection for CI optimization, code sharing and library extraction, and task orchestration/parallelization.
Follows an eight-step workflow: assess codebase size and team structure, select appropriate monorepo tooling, design workspace and project structure, configure a build caching strategy, set up affected/changed detection, implement task pipelines, configure remote caching for CI, and document conventions and workflows.
Best practices include starting with clear project boundaries, using consistent naming conventions, implementing remote caching early, keeping shared libraries focused in scope, using tags for dependency constraints, automating dependency updates, documenting the dependency graph, and setting up code ownership rules.
Integrations
Works with the major monorepo tooling ecosystem - Nx, Turborepo, Bazel, and Lerna - covering their build caching, dependency graph, and affected-detection features for CI/CD optimization. This skill is recommended for proactive use whenever a new monorepo is being set up, a build pipeline is being optimized, or development workflows are being scaled across multiple teams, rather than being invoked only after problems surface.
Who it's for
Platform and DevOps engineers setting up or scaling a monorepo across multiple teams and projects who need concrete tool selection criteria, a structured setup workflow, and caching/CI optimization practices rather than a general build-tooling overview - particularly useful when migrating from polyrepo or when CI pipelines have become slow due to unnecessary full-repo rebuilds.
Set up a new monorepo from scratch, selecting between Nx, Turborepo, Bazel, and Lerna based on codebase size and team structure.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.