Nest.js Expert

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/nestjs-expert from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

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

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Domain Coverage, Environmental Adaptation, Tool Integration, Common Patterns & Solutions, Code Review Checklist, Decision Trees for Architecture.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.