nrwl/nx-ai-agents-config
7 skills12.5k installs168 starsGitHub
Install
npx skills add https://github.com/nrwl/nx-ai-agents-configSkills in this repo
1Nx Workspacenx-workspace gives solo builders and their agents a safe, read-only playbook for understanding Nx monorepos without guessing project names or target strings. When someone asks what projects exist, how library Y is wired, or why a task cannot find configuration, the skill steers toward `nx show projects`, affected graphs since main or origin, and filters for apps versus e2e noise. That reduces wasted CI minutes and broken local commands in repos where one developer wears architect and implementer hats. It also documents practical flags—uncommitted and untracked affected sets, explicit base and head SHAs, and type filters—so pre-push checks match how indie teams actually work on feature branches. The skill explicitly covers nx command failures and missing task configuration, which places it on the build pm shelf even though ship debugging and operate incident triage benefit from the same commands. Package-manager detection via the lockfile reminder keeps agents from calling bare `nx` when only `pnpm exec nx` works.2.5kinstalls2Nx Run TasksNx Run Tasks is an agent skill that helps solo and indie builders execute work in Nx monorepos—build, test, lint, typecheck, serve, and plugin-inferred targets—using the correct project names and flags. It steers agents to inspect targets with nx show project before running commands, to use nx run for one app or library and nx run-many or nx affected when you need breadth or only changed projects. That matters when one person maintains multiple packages and cannot afford flaky copy-paste scripts from package.json alone. You will use it heavily during Build when iterating locally and during Ship when validating test and lint gates before release. The skill does not replace Nx configuration; it operationalizes the task graph your workspace already defines. Pair it with your repo’s package manager choice from lockfiles so commands actually execute in CI-like environments on a laptop.1.9kinstalls3Nx Generatenx-generate is an agent skill for solo and indie builders who maintain Nx monorepos and need consistent scaffolding without exploratory doc rabbit holes first. When you mention scaffolding, setup, project structure, creating apps or libraries, or adding a new project, the skill should run immediately—it discovers generators via the Nx CLI, applies the chosen generator with non-interactive flags, studies generator implementation and peer patterns in the repo, and confirms the result with workspace verification targets. It fits Claude Code, Cursor, Codex, and similar agents working in JavaScript or TypeScript monorepos where generators reduce boilerplate and enforce conventions. Use it as the first step before manual exploration or nx_docs for generator workflows, because the skill is designed to handle discovery internally and keep agent runs predictable.1.9kinstalls4Nx PluginsNx Plugins is a compact agent skill from the Nx AI agents config pack that tells coding agents how to extend an Nx monorepo with the right first-party plugins. Solo and indie builders use it when they want React, Node, or other stack support but do not want to hunt npm scopes manually. The skill encodes two dependable commands: list the plugin catalog with pnpm nx list, then add a plugin with pnpm nx add, mirroring how Nx documents workspace evolution. It is intentionally narrow—no graph analysis or project graph refactors—so agents stay on the happy path of official plugin installation. That makes it ideal mid-build when scaffolding landed but executors, generators, or framework integrations are still missing.1.8kinstalls5Link Workspace PackagesLink Workspace Packages is an agent skill for solo builders and small teams maintaining JavaScript monorepos under Nx or similar layouts. Install it when you generated a new library, added a cross-package import, or hit resolution errors such as cannot find module, failed to resolve import, TS2307, or unresolved @org/* paths. The skill tells the agent to detect the package manager from packageManager or the root lockfile, then link consumer to provider using the manager’s workspace commands—not tsconfig path aliases or manual dependency guesswork. It covers pnpm’s workspace: protocol and filter flags, with parallel guidance for yarn, npm, and bun workflows in the full SKILL.md. Success means dependencies appear correctly in package.json and symlinks exist under the consumer’s node_modules. It is Build-phase integration work aimed at agents in Claude Code, Cursor, and Codex that edit repos directly.1.7kinstalls6Nx ImportNx Import (ESLint) is a narrow agent skill in the Nx AI agents config repo that documents what breaks ESLint-wise when you run nx import on an existing package. Solo builders consolidating repos into an Nx monorepo use it after import to understand how @nx/eslint/plugin scans flat and legacy configs, creates cached eslint:lint targets, and conflicts with npm-script lint targets cloned from the source package.json. The skill tells you to accept auto-install of @nx/eslint, trim duplicate lint scripts while preserving lint:fix where no inferred fix target exists, and align production namedInputs so config churn does not bust unrelated caches. It also points to legacy .eslintrc pitfalls when eslint runs across generated artifacts. Pair it with the generic nx import skill for dependency hoisting, pnpm workspace globs, and TypeScript project references so your agent fixes the full import fallout, not only ESLint duplication.1.4kinstalls7Monitor CiMonitor CI is an agent skill for Nx monorepos that turns Nx Cloud CI outcomes into a scripted fix workflow instead of ad-hoc triage. Solo and indie builders shipping libraries or apps on Nx use it when a pipeline reports fixable failures and the agent must decide whether to auto-apply, verify locally, fetch heavy failure summaries, or escalate to manual review. The skill documents status-specific flows—reporting autoApplySkipReason, parallelizing verifiable task IDs, and gating destructive paths with local-fix gates—so procedural knowledge stays consistent across Claude Code runs. It pairs naturally with Nx task runners and MCP-based fix application, reducing context switching between terminal, CI UI, and patch tools. Use it during active ship cycles when CI is the bottleneck; skip it if you are not on Nx/Nx Cloud or you only need one-off local test commands without pipeline integration.1.3kinstalls