domains / families / software-engineering / monorepo-architect

monorepo-architect

combined

Design monorepo structure, build systems, and dependency boundaries using Nx, Turborepo, Bazel, or Lerna. Use when setting up a monorepo, optimizing builds, or scaling development workflows. 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.

When to use

• 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

When not to use

• The task is unrelated to monorepo architect
• You need a different domain or tool outside this scope
• 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.

Skill page

Conflict

The two copies are nearly identical, but the sickn33 copy adds a Limitations section and modifies the remote-caching best practice to include security and authorization constraints. The rmyndharis copy is the cleaner, more direct procedure, but the sickn33 copy contains material safety and validation steps (cache key verification, affected-build validation, secret handling) that the first copy lacks. Crowning one would hide the other's real constraints.