create-module

To scaffold a NestJS module with Clean Architecture, provide a module name and the tool generates a complete skeleton under src/modules/<name>. It creates domain, application, adapters, and infrastructure layers with placeholder files and NestJS wiring.

A domain-driven NestJS feature module uses a strict layered folder structure separating domain, application, adapters, and infrastructure. This enforces dependency rules where infrastructure depends on adapters, which depend on application, ultimately isolating domain logic from framework specifics.

Yes, you can generate use cases and ports automatically. The scaffolding process prepares placeholder files for domain entities, ports, use cases, and adapters, ensuring the feature module is ready to be extended with domain-driven logic.

Yes, this Clean Architecture scaffolding enforces strict dependency rules across layers. It structures the module so Infrastructure points to Adapters, Adapters point to Application, and Application points to Domain, ensuring no leakage of framework specifics into domain logic.

The best way to eliminate boilerplate is using a module scaffolding tool that automatically generates conventional directory structures and placeholder files. This ensures consistent layering and naming conventions across the codebase without manual repetitive folder creation.