NestJS Features, Scaling, and Performance

Choose the NestJS primitive whose lifecycle matches the concern. Diagnose the limiting resource before optimizing or distributing the system.

Pre-execution conflict guard

Run this guard after identifying every applicable skill and before editing files, installing packages, generating code, changing infrastructure, or executing any other state-changing command. Read-only repository and runtime inspection is allowed while resolving the guard.

Prerequisites

• Read repository instructions, installed versions, bootstrap and transport setup, deployment configuration, relevant tests, and the coordination contract of every other active skill.
• Identify the requested runtime outcome, public and operational contracts, baseline evidence, and the files, environments, and commands likely to be affected.
• Do not choose a framework feature, dependency, optimization, or deployment action before its lifecycle and evidence requirements are known.

Primary ownership

This skill leads decisions about NestJS lifecycle features, API and transport contracts, error mapping, security controls, test-layer selection, queues and schedulers, runtime reliability, observability, performance evidence, CI/CD, containers, Kubernetes, rollout, and recovery.

It shares provider/module placement with nestjs-architecture-principles and shares collaborator design with nestjs-oop-design-patterns. It yields capability, data/write, transaction, dependency, and service boundaries to the architecture skill. It yields local object responsibilities, invariant placement, and design-pattern selection to the OOP skill.