Next.js Production Platform
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.
When to Apply
Use this skill when:
- Writing or reviewing Dockerfiles, standalone output, static export, or deployment workflow changes
- Self-hosting Next.js across multiple instances or regions
- Configuring shared cache handlers, deployment IDs, or Server Action encryption keys
- Adding
instrumentation.ts, OpenTelemetry, Speed Insights, or production logging
- Splitting apps with Multi-Zones or designing tenant routing
- Choosing whether a platform supports streaming, PPR, ISR, route handlers, or WebSockets
Load On Demand
Start 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:
- Why the pattern matters
- Incorrect and correct examples
- Dataset path with larger examples
- Official source references
Rule Categories by Priority
| Priority |
Category |
Impact |
Prefix |
| 1 |
Deployment & Runtime |
CRITICAL |
deploy- |
| 2 |
Architecture & Routing Topology |
HIGH |
arch- |
| 3 |
Operations & Observability |
HIGH |
ops- |
Source Policy
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.
1---2name: nextjs-production-platform3description: 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.4---56# Next.js Production Platform78Use 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.910## When to Apply1112Use this skill when:13- Writing or reviewing Dockerfiles, standalone output, static export, or deployment workflow changes14- Self-hosting Next.js across multiple instances or regions15- Configuring shared cache handlers, deployment IDs, or Server Action encryption keys16- Adding `instrumentation.ts`, OpenTelemetry, Speed Insights, or production logging17- Splitting apps with Multi-Zones or designing tenant routing18- Choosing whether a platform supports streaming, PPR, ISR, route handlers, or WebSockets1920## Load On Demand2122Start with this file. Load detailed files only when the task needs them:2324```25references/_sections.md26references/deploy-standalone-docker.md27references/deploy-server-actions-key.md28references/deploy-cache-coordination.md29references/ops-instrumentation.md30references/arch-multi-zones.md31references/arch-multi-tenant.md32dataset/deploy/standalone-docker/correct.ts33sources/inventory.json34```3536Each rule file includes:37- Why the pattern matters38- Incorrect and correct examples39- Dataset path with larger examples40- Official source references4142## Rule Categories by Priority4344| Priority | Category | Impact | Prefix |45|----------|----------|--------|--------|46| 1 | Deployment & Runtime | CRITICAL | `deploy-` |47| 2 | Architecture & Routing Topology | HIGH | `arch-` |48| 3 | Operations & Observability | HIGH | `ops-` |4950## Source Policy5152Prefer 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.
xirothedev