nx-workspace-patterns

Configure module boundaries in an Nx monorepo by applying ESLint rules in the `.eslintrc.json` file to enforce dependency constraints and maintain a clean architecture. This prevents unauthorized cross-project imports, ensuring your workspace structure remains scalable and manageable.

The best way to set up build caching for an Nx workspace is configuring `nx.json` for local caching, then connecting Nx Cloud or a self-hosted caching instance. This optimizes build times by reusing cached task outputs across local development and CI environments.

Use `nx affected` in CI/CD workflows to run only tasks on projects changed by a commit, dramatically reducing pipeline execution time. You can implement this in GitHub Actions to automatically build, test, and lint only the modified portions of your monorepo.

Yes, you can create custom Nx generators to automate workspace configuration by defining dynamic code generation templates. This standardizes project scaffolding, enforces architectural patterns, and accelerates developer onboarding across your monorepo.

Yes, this Skill provides production patterns for managing complex Nx monorepos, addressing challenges in efficient project management and dependency handling. It supplies templates for `nx.json`, module boundary enforcement, and CI integration to ensure efficient development workflows.