Nestjs Best Practices

This one gives Claude a solid foundation in NestJS conventions: modular architecture, dependency injection scoping, exception filters, DTO validation with class-validator, and Drizzle ORM integration. You get enforcement rules for keeping modules focused, choosing the right provider scope (singleton vs request vs transient), and structuring the request pipeline correctly. The references break down common anti-patterns like dumping everything in AppModule or skipping validation. Most useful when you're setting up a new NestJS project or reviewing code that's grown messy. The Drizzle patterns are a nice touch since that's less commonly documented than TypeORM approaches.

skills.sh installs: 4K
GitHub stars: 369
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill nestjs-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

NestJS Best Practices

Overview

Grounded in the Official NestJS Documentation, this skill enforces modular architecture, dependency injection scoping, exception filters, DTO validation with class-validator, and Drizzle ORM integration patterns.

When to Use

Designing/refactoring NestJS modules or dependency injection
Creating exception filters, validating DTOs, or integrating Drizzle ORM
Reviewing code for anti-patterns or onboarding to a NestJS codebase

Instructions

1. Modular Architecture

Follow strict module encapsulation. Each domain feature should be its own @Module():

Export only what other modules need — keep internal providers private
Use forwardRef() only as a last resort for circular dependencies; prefer restructuring
Group related controllers, services, and repositories within the same module
Use a SharedModule for cross-cutting concerns (logging, configuration, caching)

See references/arch-module-boundaries.md for enforcement rules.