What problem does it solve?
This Skill helps fix a drifting or messy NestJS codebase by enforcing a clear, enterprise-friendly module-per-feature structure that reduces risky refactors and architectural inconsistency.
Core Features & Use Cases
- Module-per-feature organization: Keeps controllers, services, and the module definition co-located per feature to preserve NestJS module boundaries.
- Clean separation of NestJS primitives vs shared code: Places guards/pipes/interceptors/filters in src/common while keeping plain DTOs/utilities in src/shared.
- Safe refactoring via DI rules: Prevents critical anti-patterns like direct instantiation with
new and business logic living in controllers.
Quick Start
Ask your agent to reorganize the project into the required NestJS folders and adjust controllers/services to use constructor dependency injection while moving guards/pipes into src/common and environment/config validation into src/config.