nextjs-deployment

nextjs-deployment provides a curated set of production deployment patterns for Next.js applications. It addresses the recurring difficulty of getting a Next.js app reliably into production: choosing the right output mode, building small container images, wiring CI/CD, handling environment variables and secrets correctly, and adding health checks and observability. The skill packages battle-tested configurations rather than requiring the developer to assemble them from scattered docs.

Capabilities span standalone output configuration in next.config.ts, multi-stage Dockerfiles (non-root nextjs user, HEALTHCHECK against an /api/health endpoint, multi-arch builds), and GitHub Actions workflows for lint/type-check/test/build, Docker build-and-push to GHCR, deploys to AWS ECS and Vercel, and security scanning (npm audit, CodeQL, Trivy). It documents the distinction between NEXT_PUBLIC_ build-time/browser variables and server-only secrets, and shows generating a Server Actions encryption key at build time with openssl. Secrets are passed via GitHub Actions secrets and OIDC role assumption rather than being hardcoded, and reference files expand on Docker patterns, GitHub Actions, monitoring (OpenTelemetry), and deployment platforms.

It targets Next.js developers and DevOps engineers who are containerizing an app, setting up CI/CD pipelines, configuring preview/staging environments, or adding monitoring and health checks. The allowed tools (Read, Write, Edit, Bash) let it scaffold Dockerfiles, workflow YAML, and config files. The security-relevant operations it shows — key generation and secret handling — follow standard, non-exfiltrating practices.