Automated summary
Guides execution of Nx generators in a monorepo, prioritizing internal workspace-plugin generators ahead of core Nx ones.
Strengths
- Establishes a clear priority order: internal tooling first, standard Nx generators as fallback
- Includes verification steps (dry-run, affected-project tests, Prettier formatting)
- Leverages the nx_generators and nx_generator_schema MCP tools to inspect options before running
- Provides concrete command examples such as a Maven version bump and plugin scaffolding
Limitations
- Assumes an Nx monorepo with an internal plugin under tools/workspace-plugin and a configured nx-mcp MCP server
- Does not cover generator failure handling or rollback procedures
- Discovery steps are described without the actual commands in some sections
Use it when you need to scaffold code, create a new library or app, or automate a repetitive setup task in an Nx monorepo.
Avoid it on projects that don't use Nx, or when the nx-mcp MCP server isn't available in the environment.
Security analysis
SafeThe skill only instructs the agent to run Nx generators, inspect schemas via MCP tools, and verify generated files. It uses Bash and file-reading tools for legitimate monorepo scaffolding, with no destructive, exfiltrating, obfuscated, or safety-disabling behavior.
No concerns found
How this analysis is madeExamples
Bump the Maven plugin version to 0.0.10 with nxVersion 22.1.0-beta.7 using the workspace-plugin generator instead of editing files by hand.Create a new create-nodes plugin called my-custom-plugin in this monorepo using the workspace-plugin generator.Scaffold a new React library in the monorepo β check the workspace-plugin generators first, and fall back to @nx/react if none fit.name: run-nx-generator description: Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo. allowed-tools: Bash, Read, Glob, Grep, mcp__nx-mcp__nx_generators, mcp__nx-mcp__nx_generator_schema
Run Nx Generator
This skill helps you execute Nx generators efficiently, with special focus on workspace-plugin generators from your internal tooling.
Generator Priority List
Use the mcp__nx-mcp__nx_generator_schema tool to get more information about how to use the generator
Choose which generators to run in this priority order:
π₯ Workspace-Plugin Generators (High Priority)
These are your custom internal tools in tools/workspace-plugin/
π¦ Core Nx Generators (Standard)
Only use these if workspace-plugin generators don't fit:
nx generate @nx/devkit:...- DevKit utilitiesnx generate @nx/node:...- Node.js librariesnx generate @nx/react:...- React components and apps- Framework-specific generators
How to Run Generators
-
List available generators:
-
Get generator schema (to see available options): Use the
mcp__nx-mcp__nx_generator_schematool to get more information about how to use the generator -
Run the generator:
nx generate [generator-path] [options] -
Verify the changes:
- Review generated files
- Run tests:
nx affected -t test - Format code:
npx prettier --write [files]
Best Practices
- β Always check workspace-plugin first - it has your custom solutions
- β
Use
--dry-runflag to preview changes before applying - β Format generated code immediately with Prettier
- β Test affected projects after generation
- β Commit generator changes separately from manual edits
Examples
Bumping Maven Version
When updating the Maven plugin version, use the workspace-plugin generator:
nx generate @nx/workspace-plugin:bump-maven-version \
--newVersion 0.0.10 \
--nxVersion 22.1.0-beta.7
This automates all the version bumping instead of manual file edits.
Creating a New Plugin
For creating a new create-nodes plugin:
nx generate @nx/workspace-plugin:create-nodes-plugin \
--name my-custom-plugin
When to Use This Skill
Use this skill when you need to:
- Generate new code or projects
- Scaffold new features or libraries
- Automate repetitive setup tasks
- Update internal tools and configurations
- Create migrations or version updates
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/run-nx-generator-mryiqgog/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/run-nx-generator-mryiqgog' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/run-nx-generator-mryiqgog/download' --output '.skill-downloads/run-nx-generator-mryiqgog/SKILL.md.part' && mv '.skill-downloads/run-nx-generator-mryiqgog/SKILL.md.part' '.skill-downloads/run-nx-generator-mryiqgog/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash, Read, Glob, Grep, mcp__nx-mcp__nx_generators, mcp__nx-mcp__nx_generator_schema
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/run-nx-generator-mryiqgog/SKILL.md' && test -s '.skill-downloads/run-nx-generator-mryiqgog/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/run-nx-generator' && cp -R '.skill-downloads/run-nx-generator-mryiqgog' '.claude/skills/run-nx-generator'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js β₯ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/run-nx-generator-mryiqgog'openskills read 'run-nx-generator-mryiqgog'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/run-nx-generator-mryiqgog/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.