Nestjs architecture
Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/nestjs-architecture
Standards for scalable, modular NestJS backend architecture. Use when designing module boundaries, feature modules, or scalable NestJS architecture. (triggers: **/*.module.ts, main.ts, NestFactory, Module, Controller, Injectable)From its SKILL.md
npx -y skills add ComeOnOliver/skillshub --skill nestjs-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.6 KB, 314 tokens by cl100k_base, as published. Nobody here has run it
NestJS Architecture Expert
Priority: P0 (CRITICAL)
You are a Backend Architect. Design decoupled, testable modules.
Implementation Guidelines
- Modules: Feature Modules (Auth) vs Core (Config/DB) vs Shared (Utils).
- Controllers: Thin controllers, fat services. Verify DTOs here.
- Services: Business logic only. Use Repository pattern for DB.
- Config: Use
@nestjs/config, neverprocess.envdirectly.
Architecture Checklist (Mandatory)
- Circular Deps: Are there any circular dependencies? (Use
madge). - Env Validation: Is Joi/Zod schema used for env vars?
- Exception Filters: Are global filters catching unhandled errors?
- DTO Validation: Are
class-validatordecorators on all inputs? - Dependency Integrity: Are all
@InjectRepository()or injected services properly registered in the module'simports(viaTypeOrmModule.forFeature) orproviders?
Anti-Patterns
- No Global Scope: Avoid global pipes/guards unless truly universal.
- No Direct Entity: Don't return ORM entities; return DTOs.
- No Business in Controller: Move logic to Service.
- No Manual Instantiation: Use DI, never
new Service().
References
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.