Nestjs Best Practices
ListedEnsures NestJS projects adhere to xirothedev's curated best practices for maintainable, scalable, and secure backend development.
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 xirothedev/agent-skills --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
xirothedev
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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: stripe.com.
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.
Hosts contacted
stripe.comundeclaredWhat it found
- skills/nestjs-best-practices/rules/architecture-thin-controllers.md:432contacts stripe.com
const response = await axios.post('https://stripe.com/charges', data);
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 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 xirothedev/agent-skills at 0c98fc9cac.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0c98fc9cac
- Scanned
- 38 files, 13,659 lines
About this skill
The nestjs-best-practices skill empowers AI agents to generate, refactor, and debug NestJS applications by adhering to industry-standard architecture patterns. It ensures code aligns with modular design principles, dependency injection strategies, and robust error handling mechanisms specific to the framework.
When to use it
- Scaffold new microservices or monolithic applications that require strict architectural separation of concerns.
- Refactor legacy Node.js codebases to leverage NestJS decorators, guards, interceptors, and pipes for better maintainability.
- Debug complex runtime issues related to module lifecycle management or circular dependencies.
- Generate unit and integration tests following the official testing strategies recommended by the NestJS community.
Key capabilities
- Generates code compliant with the official NestJS architecture (Modules, Controllers, Providers).
- Implements dependency injection using
@Injectable()and constructor parameter injection. - Creates custom decorators, guards, interceptors, and pipes for request/response manipulation.
- Structures projects to support scalable microservices communication via HTTP or gRPC.
Example prompts
- "Create a NestJS module for user authentication that includes a guard for JWT verification and an interceptor for logging."
- "Refactor this existing Express.js route handler into a NestJS controller using dependency injection and input validation pipes."
- "Generate a comprehensive test suite for a service that processes payment transactions, ensuring coverage for edge cases."
Tips & gotchas
Ensure your AI agent understands the distinction between @Injectable() classes and providers to avoid circular dependency errors. When requesting microservices architecture, explicitly specify the communication protocol (e.g., gRPC or HTTP) to get accurate boilerplate code.