nx-generate

To scaffold an Nx workspace library safely, you need local generator discovery and dry-run validation to align new code with existing repository conventions. This prevents incorrect file placement and workspace drift during app or library creation.

Non-interactive Nx app creation uses discovered local generators to apply safe defaults without manual prompts. This approach enforces source inspection and post-generation verification to ensure the new application matches your established workspace structure.

Yes, custom Nx generators can execute code migrations by applying workspace-specific workflows. The process requires identifying available local and plugin generators first, then running them with non-interactive execution to safely update repository artifacts.

Dry-run verification is strongly encouraged when scaffolding Nx projects to prevent broken builds and incorrect file placement. It allows you to inspect generated sources and validate the output against existing repository patterns before committing changes.

Nx generator output may diverge from your monorepo structure if local generator discovery and repo pattern matching are skipped. Aligning new artifacts with established workspace conventions requires source inspection and applying safe generation workflows.

No external dependencies are required to use the nx-generate skill for workspace scaffolding. It relies entirely on discovering local and plugin generators already present in your Nx-based codebase to execute non-interactive project creation.