
This handles the tedious parts of Nx monorepo setup that trip up most teams. It generates proper nx.json configurations with optimized caching, sets up module boundary rules that actually enforce clean architecture, and includes working project.json templates for apps and libraries. The ESLint rules it creates prevent libraries from importing the wrong things, which saves you from circular dependencies and architectural drift. Most useful when you're moving beyond a single-app setup or inheriting an Nx workspace that's become a mess. The custom generator templates are solid starting points for your own library patterns.
$ npx -y skills add wshobson/agents --skill nx-workspace-patterns --agent claude-codeInstalls into .claude/skills of the current project.
Production patterns for Nx monorepo management.
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
| Type | Purpose | Example |
|---|---|---|
| feature | Smart components, business logic | feature-auth |
| ui | Presentational components | ui-buttons |
| data-access | API calls, state management | data-access-users |
| util | Pure functions, helpers | util-formatting |
| shell | App bootstrapping | shell-web |
Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.
Sponsors