mcpField
N
nestjs-expert

nestjs-expert

github.com/sickn33Development48.7k2.7k installsUpdated 1d ago
Repository

About nestjs-expert

nestjs-expert is a skill for working on Nest.js projects, aimed at developers implementing or reviewing Node.js applications. It guides repository inspection, Nest.js patterns, and ordered validation while emphasizing authorization and deployment safeguards.

Key features

  1. 01Detects Nest.js setup and modules
  2. 02Guidance on dependency injection and decorators
  3. 03Covers middleware, guards, interceptors, and pipes
  4. 04Reviews testing and database integration
  5. 05Orders validation from typecheck to e2e

Use cases

  1. 01Reviewing Nest.js application architecture
  2. 02Implementing authentication or database changes
  3. 03Validating a Nest.js project after modifications

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill nestjs-expert

After installing, type/nestjs-expertin Claude Code to confirm it loaded.

Bundled filesreferences/detailed-guide.md

Details

From the project README

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:
  1. If a more specialized expert fits better, use relevant specialist guidance if available while continuing the authorized task:

    • Pure TypeScript type issues → typescript-type-expert
    • Database query optimization → database-expert
    • Node.js runtime issues → nodejs-expert
    • Frontend React issues → react-expert

    These names are optional references, not proof that subagents are available or authorized.

  2. Detect Nest.js project setup using internal tools first (Read, Grep, Glob)

  3. Identify architecture patterns and existing modules

  4. Apply appropriate solutions following Nest.js best practices

  5. Validate in order: typecheck → unit tests → integration tests → e2e tests

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Evidence and deployment limits

Issue numbers, frequency/vote counts and “proven” labels in the guide are unverified historical examples, not current evidence or guarantees. Inspect the pinned Nest/ORM/adapter versions and project scripts; grep on package.json does not establish the installed version and nest info is not dependency-graph validation. Snippets omit imports/types and are adapter-specific. Preserve validation, object/tenant authorization and fail-closed guards; JWT claims alone do not isolate tenants. Do not expose inspector ports or heap snapshots publicly: they may disclose secrets. Database migrations, downgrades, schema synchronization and production restarts need a concrete reviewed rollback/data plan. Separate unit mocks from authorized isolated integration databases and report which tests actually ran.

Comments

Markdown supported