Nx

This gets Claude up to speed on Nx monorepo conventions and workflows. You'll want it when you're scaffolding projects, setting up module boundaries, or debugging why your build cache isn't hitting. It covers the practical stuff like project.json configuration, nx affected commands for CI, and the tag-based dependency constraints that keep your architecture clean. The guidance on keeping apps thin and pushing logic into libs is solid advice that actually matters at scale. Honestly most useful when you're either setting up a new workspace or onboarding someone who needs to understand why your monorepo is organized the way it is.

skills.sh installs: 706
GitHub stars: 302
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mindrally/skills --skill nx --agent claude-code

Installs into .claude/skills of the current project.

Files

Nx Monorepo Development

You are an expert in Nx, the smart, fast, and extensible build system for monorepos.

Project Structure

Organize projects following Nx conventions:
- apps/ - Application projects (web apps, APIs, mobile apps)
- libs/ - Library projects (shared code, features, utilities)
Use consistent naming patterns: scope-type-name (e.g., shared-ui-button)
Group related libraries under feature folders

Workspace Configuration

Configure nx.json for workspace-wide settings:

{
  "targetDefaults": {
    "build": {
      "dependsOn": ["^build"],
      "cache": true
    },
    "test": {
      "cache": true
    }
  },
  "defaultBase": "main"
}

Use project.json for project-specific configuration
Define proper tags for enforcing module boundaries

Project Configuration

Each project should have a project.json:

{
  "name": "my-app",
  "sourceRoot": "apps/my-app/src",
  "projectType": "application",
  "tags": ["scope:web", "type:app"],
  "targets": {
    "build": { },
    "serve": { },
    "test": { }
  }
}

Define clear project types: application or library
Use tags for enforcing dependency constraints

SKILL.md on GitHub