메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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 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 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 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.
SOC 직업 분류 기준
| name | nextjs-production-platform |
| description | 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. |
| metadata | {"author":"xiro","version":"0.1.0","organization":"local","date":"May 2026","framework":"Next.js","frameworkVersion":"v16.2.6","supportedVersions":["15.x.x","16.x.x"],"priority":"high","abstract":"Production platform skill for deploying and operating Next.js applications across Docker, standalone Node runtime, self-hosted multi-instance setups, observability, multi-zone, and multi-tenant architectures."} |
Use this skill when a Next.js task touches runtime packaging, hosting topology, observability, cache coordination, or domain routing. Verify platform capabilities before choosing a rendering, cache, or deployment mode.
Use this skill when:
instrumentation.ts, OpenTelemetry, Speed Insights, or production loggingStart with this file. Load detailed files only when the task needs them:
references/_sections.md
references/deploy-standalone-docker.md
references/deploy-server-actions-key.md
references/deploy-cache-coordination.md
references/ops-instrumentation.md
references/arch-multi-zones.md
references/arch-multi-tenant.md
dataset/deploy/standalone-docker/correct.ts
sources/inventory.json
Each rule file includes:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Deployment & Runtime | CRITICAL | deploy- |
| 2 | Architecture & Routing Topology | HIGH | arch- |
| 3 | Operations & Observability | HIGH | ops- |
Prefer official Next.js deployment, self-hosting, adapter, and platform docs. Verify host-specific behavior from the host documentation before assuming support for streaming, PPR, shared cache, or long-running connections.