메뉴
Use for NestJS production worker and integration tasks involving microservice transports, hybrid apps, queues, scheduled jobs, cache stores, health checks, structured logging, lifecycle events, shutdown hooks, WebSocket gateways, or non-HTTP Nest runtimes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use for production NestJS API contract work involving OpenAPI/Swagger, DTO validation, versioning, public error envelopes, guards and policy authorization, rate limiting behind proxies, CORS/helmet/cookie hardening, or file upload boundaries.
Use for Next.js 16 Cache Components and runtime rendering work involving `use cache`, `cacheLife`, `cacheTag`, `updateTag`, Suspense, runtime APIs, Partial Prerendering, remote cache, metadata/viewport runtime access, or migration from older route segment caching configs.
Use for real projects that combine a Next.js frontend/BFF with a NestJS API. Covers ownership boundaries, OpenAPI client generation, session and auth propagation, CORS/proxy contracts, Server Component data fetching, shared environment contracts, and split deployment/runtime alignment.
Use for production Next.js platform work involving Docker or standalone output, static export tradeoffs, self-hosting, deployment adapters, Server Actions encryption keys, shared cache coordination, OpenTelemetry instrumentation, multi-zones, multi-tenant routing, or platform capability reviews.
Use for security-sensitive Next.js backend-for-frontend work involving Route Handlers, Proxy, Server Actions, webhooks, callbacks, data access layers, server-only modules, request validation, rate limits, or public API boundaries. Prefer this skill when a Next.js task exposes HTTP endpoints or moves privileged data across server/client boundaries.
Highest-priority for all NestJS-related tasks involving API engineering. Use this skill whenever writing, reviewing, refactoring, debugging, or planning NestJS backend/API code using @nestjs/*, modules, providers, controllers, DTOs, pipes, guards, interceptors, exception filters, Prisma or TypeORM services, GraphQL resolvers, microservices, queues, caching, configuration, observability, or NestJS tests. Prefer this skill over generic Node.js or backend advice for NestJS code.
| name | nestjs-workers-transports-ops |
| description | Use for NestJS production worker and integration tasks involving microservice transports, hybrid apps, queues, scheduled jobs, cache stores, health checks, structured logging, lifecycle events, shutdown hooks, WebSocket gateways, or non-HTTP Nest runtimes. |
Use this skill when NestJS runs work outside a plain HTTP controller: message handlers, queue processors, scheduled jobs, gateways, cache-backed flows, or health/observability surfaces.
Use this skill when:
@MessagePattern, Kafka/RabbitMQ/NATS/gRPC transports, or hybrid apps@Cron, intervals, scheduler registry jobs, or distributed scheduled tasksStart with this file. Load detailed files only when the task needs them:
references/_sections.md
references/transport-microservice-errors.md
references/transport-hybrid-config.md
references/ops-queue-idempotency.md
references/ops-scheduler-locks.md
references/ops-cache-store.md
references/ops-health-logging.md
dataset/ops/queue-idempotency/correct.ts
sources/inventory.json
Each rule file includes:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Transports & Integration Patterns | CRITICAL | transport- |
| 2 | Operations & Worker Runtime | CRITICAL | ops- |
| 3 | Performance & Runtime State | HIGH | perf- |
Prefer official NestJS docs for microservices, queues, scheduling, caching, health checks, logging, and lifecycle semantics. Broker-specific reliability settings must be verified against the chosen broker and queue library docs.