NestJS Framework Expert

Category

Backend & Frameworks

⚠️ MANDATORY COMPLIANCE ⚠️

CRITICAL: The 6-step workflow outlined in this document MUST be followed in exact order for EVERY NestJS engagement. Skipping steps or deviating from the procedure will result in incomplete or unsafe guidance. This is non-negotiable.

File Structure

• SKILL.md (this file): Main instructions and MANDATORY workflow

Step 1: Initial Analysis

Gather inputs and determine scope and requirements.

Step 2: Load Memory

Load project-specific memory via MemoryStore interface.

Step 3: Load Context

Load relevant context files via ContextProvider interface.

Step 4: Core Implementation

Execute the skill-specific core action.

Step 5: Generate Output

Create deliverables and save to /claudedocs/ following OUTPUT_CONVENTIONS.md.

Step 6: Update Memory

Update project memory with new patterns and decisions.

Interface References

• Context: Loaded via ContextProvider Interface

• Memory: Accessed via MemoryStore Interface

• Shared Patterns: Shared Loading Patterns

Focus Areas

• Module Architecture: feature modules, shared modules, dependency boundaries

• Controllers & Providers: DI scopes, service layering, lifecycle hooks

• Validation & DTOs: class-validator, pipes, transformation

• Data Access: TypeORM/Prisma patterns, transactions, migrations

• Security: guards, auth strategies, rate limiting, secrets

• Messaging: microservices, queues, event-driven patterns

• Testing: unit + e2e setup, test modules, mocking

Purpose

Enterprise-grade NestJS development guidance for building modular, testable Node.js backends with TypeScript. Covers module design, dependency injection, validation, security, performance, and deployment.

MANDATORY WORKFLOW (MUST FOLLOW EXACTLY)

⚠️ STEP 1: Scope the NestJS Engagement (REQUIRED)

YOU MUST:

• Identify NestJS version and runtime environment

• Clarify the domain (API, microservice, hybrid) and deployment target

• Determine ORM/transport stack (TypeORM, Prisma, Redis, RabbitMQ)

• Ask clarifying questions about auth, messaging, and module boundaries

• Think through your implementation plan in a <thinking> block before writing any files or recommending changes

DO NOT PROCEED WITHOUT A CLEAR SCOPE AND PLAN

⚠️ STEP 2: Load Project Memory (REQUIRED)

YOU MUST:

• Load memory with memoryStore.getSkillMemory("nestjs", "{project-name}")

• Review cross-skill memory with memoryStore.getByProject("{project-name}")

• Note existing module conventions and integrations

DO NOT PROCEED WITHOUT CHECKING MEMORY

⚠️ STEP 3: Load Context (REQUIRED)

YOU MUST:

• Use contextProvider.getDomainIndex("engineering") for general architecture patterns

• Pull security context with contextProvider.getCrossDomainContext("engineering", ["auth", "security"])

• Stay within the declared file budget

DO NOT PROCEED WITHOUT RELEVANT CONTEXT

⚠️ STEP 4: Analyze Architecture & Code Paths (REQUIRED)

YOU MUST:

• Review module boundaries, controller routes, and provider scopes

• Inspect DTO validation, pipes, and exception filters

• Evaluate data access patterns and transaction handling

• Check integration points (queues, caches, external services)

DO NOT PROCEED WITHOUT A COMPLETE ANALYSIS

⚠️ STEP 5: Provide NestJS Guidance (REQUIRED)

YOU MUST:

• Recommend module restructuring or DI improvements

• Provide validation, security, and testing guidance

• Suggest performance or messaging enhancements

DO NOT PROVIDE GENERIC OR UNSUPPORTED RECOMMENDATIONS

⚠️ STEP 6: Generate Output & Update Memory (REQUIRED)

YOU MUST:

• Produce a structured report in /claudedocs/nestjs_{project}_{YYYY-MM-DD}.md

• Follow the naming conventions in ../OUTPUT_CONVENTIONS.md

• Update memory with memoryStore.update("nestjs", "{project-name}", ...) :

• project_overview.md

• module_map.md

• integration_notes.md

• testing_strategy.md

DO NOT FINISH WITHOUT SAVING OUTPUT AND UPDATING MEMORY

Compliance Checklist

Before completing ANY NestJS task, verify:

• Step 1: Scope defined and plan documented in <thinking>

• Step 2: Project memory loaded via memoryStore.getSkillMemory()

• Step 3: Context loaded via contextProvider

• Step 4: Architecture and code paths analyzed

• Step 5: NestJS guidance provided with actionable recommendations

• Step 6: Output saved to /claudedocs/ and memory updated

FAILURE TO COMPLETE ALL STEPS INVALIDATES THE GUIDANCE

Version History

Version Date Changes

1.0.0 2026-02-12 Initial release for NestJS framework guidance