Monorepo Architect

VerifiedSafe

Expert in monorepo architecture, build systems, and dependency management. Uses Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Ideal for monorepo setup, build optimization, or scaling workflows across teams.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude Code
#monorepo#nx#turborepo#build-systems#dependency-management

Recommended for

Our review

Expert in monorepo architecture, build systems, and dependency management at scale, mastering Nx, Turborepo, Bazel, and Lerna.

Strengths

  • Selection and configuration of the right monorepo tool (Nx, Turborepo, Bazel, Lerna)
  • CI pipeline optimization with change detection and build caching
  • Clear workspace structuring and cross-project dependency management
  • Automated affected dependency detection for incremental builds

Limitations

  • Requires prior understanding of build tools and code structure
  • May not suit very small teams or simple monolithic projects
  • Initial setup can be complex and time-consuming
When to use it

Use this skill when setting up a new monorepo, migrating from polyrepo, or optimizing slow CI pipelines with code sharing across applications.

When not to use it

Avoid this skill for tasks unrelated to monorepo architecture, such as specific feature development or using tools outside its scope.

Security analysis

Safe
Quality score90/100

The skill provides guidance on monorepo architecture without containing any executable code or commands that could compromise security.

No concerns found

Examples

Set up a new monorepo with Nx
I need to set up a new monorepo for a project with multiple React and Node.js applications. Help me choose the right tool (Nx, Turborepo, etc.) and configure the workspace structure, build caching, and dependency management.
Optimize CI pipeline with affected detection
Our monorepo CI pipeline is too slow because it builds everything on every push. Can you help me set up affected/changed detection with Nx to only build and test the projects that actually changed?
Migrate from polyrepo to monorepo
We currently have several separate repositories for our frontend, backend, and shared libraries. I want to consolidate into a single monorepo. Walk me through the migration plan, tool selection (Turborepo or Nx), and best practices for dependency management and code sharing.

name: monorepo-architect description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,"

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 PROACTIVELY for monorepo setup, 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.
  • If detailed examples are required, open resources/implementation-playbook.md.

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
  • Implement remote caching early
  • Keep shared libraries focused
  • Use tags for dependency constraints
  • Automate dependency updates
  • Document the dependency graph
  • Set up code ownership rules
Related skills