nx-generate

Automates discovering, evaluating, and executing non-interactive Nx generators for scaffolding and code structure in monorepos.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/RomerX64/flow --skill nx-generate-romerx64
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-generate
Source: https://github.com/RomerX64/flow/tree/main/.github/skills/nx-generate
Command: npx skills add https://github.com/RomerX64/flow --skill nx-generate-romerx64

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating Nx generators across a monorepo can be error-prone and time-consuming; this skill centralizes discovery, evaluation, and execution of generators to enforce consistent scaffolding and project structure.

Core Features & Use Cases

  • Discover and run local workspace generators to scaffold apps and libraries
  • Ensure non-interactive usage with --no-interactive for deterministic results
  • Read generator sources and apply dry-runs to validate changes before applying
  • Align new artifacts with existing repo patterns and build/test workflows

Quick Start

Invoke an Nx generator to scaffold or update projects in the workspace using non-interactive options.

Frequently Asked Questions about nx-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate scaffolding apps and libraries in an Nx monorepo?

Automate scaffolding in an Nx monorepo by discovering and executing local workspace generators with strict non-interactive options. This enforces consistent project structure and deterministic results without manual prompts during the code generation process.

How do I validate Nx generator changes before applying them to the workspace?

Validate Nx generator changes before applying them by reading generator sources and executing dry-runs. This approach verifies structural modifications and pattern adherence safely, ensuring new artifacts align with existing repo workflows prior to final execution.

Can I run Nx generators non-interactively for deterministic monorepo updates?

Yes, you can run Nx generators non-interactively by passing --no-interactive options. This ensures deterministic results and enforces pattern adherence during apps and libraries scaffolding, migrations, and workspace maintenance without requiring manual user input.

What is the best way to maintain consistent project structure during Nx workspace migrations?

Maintain consistent project structure during Nx workspace migrations by centralizing generator discovery and execution. This method applies non-interactive scaffolding rules and validates changes via dry-runs, ensuring new artifacts match existing repo patterns and pass build tests.

Why should I use Nx generators for TypeScript workspace maintenance instead of manual scaffolding?

Use Nx generators for TypeScript workspace maintenance because coordinating manual scaffolding is error-prone. Centralizing generator execution enforces consistent project structure, applies dry-run validation, and aligns new code with existing build and test workflows automatically.