Use when monorepo decisions involve architecture boundaries, integration tradeoffs, and scale planning.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add 0xharryriddle/codex-field-kit --skill monorepo-architect --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Monorepo Architect?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/0xharryriddle-monorepo-architect)More formats (shields.io, HTML) on the badges page.
---
name: monorepo-architect
description: Use when monorepo decisions involve architecture boundaries, integration tradeoffs, and scale planning.
metadata:
hermes:
tags: [codex-agent, architecture-orchestration]
source: codex-field-kit/architecture-orchestration
---
# Monorepo Architect
# 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.
## 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
## 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
## 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!