monorepo-architect — Claude Code subagent: overview and install
Architects scalable monorepo workspaces and build caching with Nx, Turborepo, Bazel, or Lerna. Speeds up CI pipelines by isolating affected packages.
/plugin marketplace add wshobson/agents
/plugin install developer-essentials@claude-code-workflowsWhat monorepo-architect does
Configured around the opus model, this subagent helps teams structure multi-project workspaces. It evaluates codebase scale to choose between Nx, Turborepo, Bazel, or Lerna, then designs workspace boundaries and library extraction paths.
The workflow targets CI/CD bottlenecks through task orchestration, affected package detection, and build caching. It sets dependency constraints via tags and organizes parallel task execution.
Remote caching and dependency tracking require established code ownership rules and clear package boundaries before rollout.
What it helps with
- choose between Nx, Turborepo, Bazel, or Lerna for project needs
- configure local and remote build caching to reduce CI execution time
- migrate standalone repositories into a unified monorepo workspace
- extract common business logic and UI into dedicated shared libraries
Example prompts for the agent
- Design a Turborepo workspace to combine our frontend and backend repositories.
- Configure affected task detection and remote caching for our CI pipeline.
- Extract common API client logic into an internal library within this Nx workspace.
How to install monorepo-architect
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install developer-essentials@claude-code-workflows2Manually: put the files in place
.claude/agents/monorepo-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/monorepo-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/monorepo-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about monorepo-architect
How to install monorepo-architect in Claude Code?
Run /plugin marketplace add wshobson/agents followed by /plugin install developer-essentials@claude-code-workflows.
What does monorepo-architect do?
It designs monorepo directory structures, configures task pipelines, and manages project dependency graphs to streamline builds.
Which build tools does this subagent support?
It works with Nx, Turborepo, Bazel, and Lerna, configuring dependency constraints and workspace caching for each tool.
Source text
monorepo-architect.md · MIT
--- 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, build optimization, or scaling development workflows across teams. model: opus --- # 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
© Seth Hobson · MIT · wshobson/agents