domains / families / agent-tooling / monorepo-navigator

monorepo-navigator

separate

Monorepo Navigator

When to use

• Multiple packages/apps share code (UI components, utils, types, API clients)
• Build times are slow because everything rebuilds when anything changes
• Migrating from multiple repos to a single repo
• Need to publish packages to npm with coordinated versioning
• Teams work across multiple packages and need unified tooling
• Single-app project with no shared packages
• Team/project boundaries are completely isolated (polyrepo is fine)
• Shared code is minimal and copy-paste overhead is acceptable

When not to use

• Single-app project with no shared packages
• Completely isolated team or project boundaries
• Minimal shared code where copy-paste is acceptable

Skill page

Source