- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
65 lines
2.1 KiB
Markdown
65 lines
2.1 KiB
Markdown
---
|
|
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,"
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# 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
|