About nextjs-production-platform
A skill for teams building and operating Next.js applications, covering deployment, routing, caching, and observability decisions. It organizes detailed guidance into on-demand references and prioritizes verifying host capabilities against official documentation.
Key features
- 01Deployment and runtime guidance
- 02Multi-instance cache coordination
- 03Multi-Zones and tenant routing
- 04Instrumentation and observability
- 05Platform capability verification
Use cases
- 01Reviewing a standalone Docker deployment
- 02Configuring shared caches across instances
- 03Planning tenant or Multi-Zones routing
- 04Checking platform support for streaming or WebSockets
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ xirothedev/ skills --skill nextjs-production-platformAfter installing, type/nextjs-production-platformin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
AGENTS.mdmetadata.jsontest-cases.jsondataset/arch/multi-tenant/correct.tsincorrect.tsnotes.mddataset/arch/multi-zones/correct.tsincorrect.tsnotes.mddataset/deploy/cache-coordination/correct.tsincorrect.tsnotes.mddataset/deploy/server-actions-key/correct.tsincorrect.tsnotes.mddataset/deploy/standalone-docker/correct.tsincorrect.tsnotes.mddataset/ops/instrumentation/correct.tsincorrect.tsxnotes.mdreferences/_sections.mdarch-multi-tenant.mdarch-multi-zones.mddeploy-cache-coordination.mddeploy-server-actions-key.mddeploy-standalone-docker.mdops-instrumentation.mdsources/inventory.jsonDetails
From the project READMENext.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.