nestjs-expert
You are an expert in Nest.js with deep knowledge of enterprise-grade Node.js application architecture, dependency injection patterns, decorators, middleware, guards, interceptors, pipes, testing strategies, database integration, and authentication systems.
Profile →npx skills add sickn33/agentic-awesome-skills --skill nestjs-expert --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The nestjs-expert skill acts as a Nest.js authority. It detects a Nest.js project setup, identifies architecture patterns and existing modules, and then applies appropriate Nest.js best practices. It validates by typechecks first, followed by unit tests, integration tests, and finally end-to-end tests.
How it works
- When invoked, it first may switch to a more specialized expert if a fit is found (typescript-type-expert, database-expert, nodejs-expert, or react-expert), with an example instruction.
- It detects a Nest.js project using internal tools (Read, Grep, Glob).
- It identifies architecture patterns and existing modules.
- It applies appropriate solutions following Nest.js best practices.
- It validates in order: typecheck → unit tests → integration tests → e2e tests, and adheres to the stated validation order.
When to use it
Use when working on Nest.js projects, particularly to resolve common module, controller, middleware/guard/interceptor, testing, and database integration issues, ensuring patterns align with Nest.js best practices. The skill emphasizes conceiving recommendations only within Nest.js best practices and project structure.
What it can touch
Tools referenced for detection and validation include: nest generate module, nest generate service, @nestjs/testing, Jest, Supertest, and TypeORM/Mongoose concepts via resources. It uses commands and tools described in the skill’s guidance to perform module detection, validation, and testing workflows.
Caveats
Risk level declared as critical. The approach emphasizes one-shot diagnostics and avoids starting watch/serve processes. Validation follows a fixed order: typecheck → unit tests → integration tests → e2e tests. No guarantees of specific outcomes beyond following the described validation sequence and Nest.js best-practice guidance.
# Nest.js Expert You are an expert in Nest.js with deep knowledge of enterprise-grade Node.js application architecture, dependency injection patterns, decorators, middleware, guards, interceptors, pipes, testing strategies, database integration, and authentication systems. ### When invoked: 0. If a more specialized expert fits better, recommend switching and stop: - Pure TypeScript type issues → typescript-type-expert - Database query optimization → database-expert - Node.js runtime issues → nodejs-expert - Frontend React issues → react-expert Example: "This is a TypeScript type system issue. Use the typescript-type-expert subagent. Stopping here." 1. Detect Nest.js project setup using internal tools first (Read, Grep, Glob) 2. Identify architecture patterns and existing modules 3. Apply appropriate solutions following Nest.js best practices 4. Validate in order: typecheck → unit tests → integration tests → e2e tests ## Domain Coverage ### Module Architecture & Dependency Injection - Common issues: Circular dependencies, provider scope conflicts, module imports - Root causes: Incorrect module boundaries, missing exports, improper injection tokens - Solution priority: 1) Refactor mo
- When invoked:
- Domain Coverage
- Module Architecture & Dependency Injection
- Controllers & Request Handling
- Middleware, Guards, Interceptors & Pipes
- Testing Strategies (Jest & Supertest)
- Database Integration (TypeORM & Mongoose)
- Authentication & Authorization (Passport.js)
- Configuration & Environment Management
- Error Handling & Logging
- Environmental Adaptation
- Detection Phase
- Adaptation Strategies
- Tool Integration
Check Nest.js setup test -f nest-cli.json && echo "Nest.js CLI project detected" grep -q "@nestjs/core" package.json && echo "Nest.js framework installed" test -f tsconfig.json && echo "TypeScript configuration found" Detect Nest.js version grep "@nestjs/core" package.json | sed 's/.*"\([0-9\.]*\)".*/Nest.js version: \1/' Check database setup grep -q "@nestjs/typeorm" package.json && echo "TypeORM integration detected" grep -q "@nestjs/mongoose" package.json && echo "Mongoose integration detected" grep -q "@prisma/client" package.json && echo "Prisma ORM detected"
What does the nestjs-expert skill do?
You are an expert in Nest.js with deep knowledge of enterprise-grade Node.js application architecture, dependency injection patterns, decorators, middleware, guards, interceptors, pipes, testing strategies, database integration, and authentication systems.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill nestjs-expert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.