Open Skills Logo
Open Skills

monorepo-architect

精通大规模单仓库架构、构建系统及依赖管理。擅长运用Nx、Turborepo、Bazel和Lerna工具实现高效的多项目开发流程。主动采用单仓库配置方案，

查看详情
name:monorepo-architectdescription:"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,"

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

  • Assess codebase size and team structure

  • Select appropriate monorepo tooling

  • Design workspace and project structure

  • Configure build caching strategy

  • Set up affected/changed detection

  • Implement task pipelines

  • Configure remote caching for CI

  • 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