domains / software-engineering / monorepo-architecture / monorepo-architect

monorepo-architect

Skill card

combined

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.

Repositories

Other copies

Combined skill

---
name: monorepo-architect
description: "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."
---

# 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.

## 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

## 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.

## Conflicts

- rmyndharis/antigravity-skills says 'Implement remote caching early' without security constraints; sickn33/agentic-awesome-skills requires authorization and review of private artifact/credential transmission before enabling remote caching.