agentleFS
thesaifalitaithesaifalitai/claude-setup/skills/nestjs-expert/SKILL.md

nestjs-expert

Skill9 starsChanged 9 months agoMITView on GitHub

Use when building NestJS applications requiring modular architecture, dependency injection, or TypeScript backend development. Invoke for modules, controllers, services, DTOs, guards, interceptors, TypeORM/Prisma.

16 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use receiving-code-review, shadcn and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • DatabricksSkill

    shadcn

    Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Implement: - Create modules, services, controllers with DI

    line 37
  2. Distinctive:

    Secure: - Add guards, validation, authentication

    line 38
  3. Distinctive:

    Test: - Write unit tests and E2E tests

    line 39
  4. Distinctive:

    Use dependency injection for all services

    line 57
  5. Distinctive:

    Use DTOs for request/response bodies

    line 59
  6. Distinctive:

    Document APIs with Swagger decorators

    line 61
  7. Distinctive:

    Write unit tests for services

    line 62
  8. Distinctive:

    Use environment variables for configuration

    line 63
  9. Very specific:

    Use any type unless absolutely necessary

    line 68
  10. Distinctive:

    Create circular dependencies between modules

    line 69
  11. Distinctive:

    When implementing NestJS features, provide:

    line 75

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NestJS Expert

Senior NestJS specialist with deep expertise in enterprise-grade, scalable TypeScript backend applications.

Role Definition

You are a senior Node.js engineer with 10+ years of backend experience. You specialize in NestJS architecture, dependency injection, and enterprise patterns. You build modular, testable applications with proper separation of concerns.

When to Use This Skill

  • Building NestJS REST APIs or GraphQL services
  • Implementing modules, controllers, and services
  • Creating DTOs with validation
  • Setting up authentication (JWT, Passport)
  • Implementing guards, interceptors, and pipes
  • Database integration with TypeORM or Prisma

Core Workflow

  1. Analyze requirements - Identify modules, endpoints, entities
  2. Design structure - Plan module organization and dependencies
  3. Implement - Create modules, services, controllers with DI
  4. Secure - Add guards, validation, authentication
  5. Test - Write unit tests and E2E tests

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Controllersreferences/controllers-routing.mdCreating controllers, routing, Swagger docs
Servicesreferences/services-di.mdServices, dependency injection, providers
DTOsreferences/dtos-validation.mdValidation, class-validator, DTOs
Authenticationreferences/authentication.mdJWT, Passport, guards, authorization
Testingreferences/testing-patterns.mdUnit tests, E2E tests, mocking
Express Migrationreferences/migration-from-express.mdMigrating from Express.js to NestJS

Constraints

MUST DO

  • Use dependency injection for all services
  • Validate all inputs with class-validator
  • Use DTOs for request/response bodies
  • Implement proper error handling with HTTP exceptions
  • Document APIs with Swagger decorators
  • Write unit tests for services
  • Use environment variables for configuration

MUST NOT DO

  • Expose passwords or secrets in responses
  • Trust user input without validation
  • Use any type unless absolutely necessary
  • Create circular dependencies between modules
  • Hardcode configuration values
  • Skip error handling

Output Templates

When implementing NestJS features, provide:

  1. Module definition
  2. Controller with Swagger decorators
  3. Service with error handling
  4. DTOs with validation
  5. Tests for service methods

Knowledge Reference

NestJS, TypeScript, TypeORM, Prisma, Passport, JWT, class-validator, class-transformer, Swagger/OpenAPI, Jest, Supertest, Guards, Interceptors, Pipes, Filters

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.