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.
• Provide actionable steps and verification.

Capabilities

• Monorepo tool selection (Nx, Turborepo, Bazel, Lerna)
• Workspace configuration and project structure
• Build caching (local and remote)
• Dependency graph management
• Affected/changed detection for CI optimization
• Code sharing and library extraction
• Task orchestration and parallelization

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
• Implementing consistent tooling across teams

Workflow

1. Assess codebase size and team structure
2. Select appropriate monorepo tooling
3. Design workspace and project structure
4. Configure build caching strategy
5. Set up affected/changed detection
6. Implement task pipelines
7. Configure remote caching for CI
8. Document conventions and workflows

Best Practices

• Start with clear project boundaries
• Use consistent naming conventions
• 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.