mcpField
N
nx-workspace-patterns

nx-workspace-patterns

github.com/wshobsonDevelopment41.9k11.0k installsUpdated 2w ago
Repository

About nx-workspace-patterns

A skill for teams setting up and managing Nx monorepos. It covers workspace structure, project boundaries, dependency management, caching, and CI optimization patterns.

Key features

  1. 01Nx workspace architecture
  2. 02Project boundaries and tags
  3. 03Library type organization
  4. 04Affected-command CI optimization
  5. 05Caching and migration patterns

Use cases

  1. 01Setting up an Nx workspace
  2. 02Testing only projects affected by changes
  3. 03Managing dependencies across monorepo projects
  4. 04Migrating a codebase to Nx

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wshobson/agents --skill nx-workspace-patterns

After installing, type/nx-workspace-patternsin Claude Code to confirm it loaded.

Bundled filesreferences/details.md

Details

From the project README

Nx Workspace Patterns

Production patterns for Nx monorepo management.

When to Use This Skill

  • Setting up new Nx workspaces
  • Configuring project boundaries
  • Optimizing CI with affected commands
  • Implementing remote caching
  • Managing dependencies between projects
  • Migrating to Nx

Core Concepts

1. Nx Architecture
workspace/
├── apps/              # Deployable applications
│   ├── web/
│   └── api/
├── libs/              # Shared libraries
│   ├── shared/
│   │   ├── ui/
│   │   └── utils/
│   └── feature/
│       ├── auth/
│       └── dashboard/
├── tools/             # Custom executors/generators
├── nx.json            # Nx configuration
└── workspace.json     # Project configuration
2. Library Types
TypePurposeExample
featureSmart components, business logicfeature-auth
uiPresentational componentsui-buttons
data-accessAPI calls, state managementdata-access-users
utilPure functions, helpersutil-formatting
shellApp bootstrappingshell-web

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's
  • Use tags consistently - Enforce with module boundaries
  • Enable caching early - Significant CI savings
  • Keep libs focused - Single responsibility
  • Use generators - Ensure consistency
  • Document boundaries - Help new developers
Don'ts
  • Don't create circular deps - Graph should be acyclic
  • Don't skip affected - Test only what changed
  • Don't ignore boundaries - Tech debt accumulates
  • Don't over-granularize - Balance lib count

Comments

Markdown supported