What problem does it solve? When adding new features to a NestJS backend, developers often produce inconsistent module layouts, missing Swagger documentation, or duplicated CRUD boilerplate. This Skill enforces a single architectural pattern so every module in apps/backend/src/modules looks and behaves the same. ## Core Features & Use Cases - Standardized Module Layout: Defines the exact directory structure (dto/, entities/, enum/, interfaces/) and file naming conventions for each feature module. - Base Class Inheritance: Requires controllers to extend BaseControllerOperations and services to extend BaseServiceOperations, eliminating repetitive CRUD code. - Built-in API Documentation: Mandates @ApiTags, @ApiOperation, and @ApiResponse decorators so every endpoint is documented in Swagger automatically. - Use Case: You need a new "orders" feature. Follow this Skill to scaffold orders.controller.ts, orders.service.ts, orders.module.ts, the entity, and DTOs with validation, then register the module in app.module.ts. ## Quick Start Create a new NestJS feature module named orders following the backend structure pattern with entity, DTOs, service, and controller.
