Nestjs Best Practices
CheckedGenerates NestJS code adhering to Giuseppe Trisciuoglio's best practices for robust, scalable, and maintainable backend applications.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nestjs-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
giuseppe-trisciuoglio
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned giuseppe-trisciuoglio/developer-kit at fe73fb33a0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- fe73fb33a0
- Scanned
- 10 files, 1,140 lines
About this skill
What it does
This skill generates NestJS code adhering to Giuseppe Trisciuoglio's best practices for robust, scalable, and maintainable backend applications. It enforces specific patterns including modular architecture, dependency injection scoping, exception filters, DTO validation using class-validator, and integration with the Drizzle ORM. The skill is grounded in the official NestJS documentation and aims to improve code quality and consistency within NestJS projects.
When to use it
- Designing or refactoring existing NestJS modules and dependency injection configurations.
- Creating custom exception filters, validating Data Transfer Objects (DTOs), or integrating with Drizzle ORM.
- Reviewing NestJS code for potential anti-patterns or when onboarding new developers to a project.
Key capabilities
- Enforces modular architecture principles: exporting only necessary components and grouping related functionality within modules.
- Provides guidance on dependency injection scoping (DEFAULT, REQUEST, TRANSIENT) with recommendations for appropriate use cases.
- Outlines the NestJS request lifecycle pipeline (Middleware → Guards → Interceptors → Pipes → Route Handler → Exception Filters).
- Promotes DTO validation using
class-validator. - Supports integration with Drizzle ORM.
Example prompts
- "Generate a NestJS module for user authentication, following best practices."
- "Show me an example of a REQUEST scoped dependency injection provider in NestJS."
- "Create a DTO validation filter using class-validator and NestJS."
Tips & gotchas
- The skill prioritizes strict modularity; circular dependencies should be avoided whenever possible.
- Default to the
DEFAULTscope for dependency injection unless a specific need (request or transient) is justified. - Familiarize yourself with the NestJS request lifecycle pipeline to understand where different components fit within the application flow.