deployment-guide

Generates platform-specific deployment documentation with environment variable checklists and troubleshooting guides.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/human-centric-engineering/resparkable --skill deployment-guide-human-centric-engineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-guide
Source: https://github.com/human-centric-engineering/resparkable/tree/main/.claude/skills/deployment-guide
Command: npx skills add https://github.com/human-centric-engineering/resparkable --skill deployment-guide-human-centric-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a Next.js application to a new hosting platform requires assembling scattered configuration details: environment variables, build commands, database migration steps, and health checks. This Skill consolidates that knowledge into ready-to-use, platform-specific deployment documentation so you avoid misconfigured secrets, failed migrations, and broken authentication in production. ## Core Features & Use Cases - Platform Templates: Pre-built configuration for Vercel, Railway, Render, Fly.io, Docker self-hosted, DigitalOcean, and AWS, including railway.json, render.yaml, fly.toml, and Nginx reverse proxy examples. - Environment Variable Checklists: Complete lists of required and optional variables (DATABASE_URL, BETTER_AUTH_SECRET, RESEND_API_KEY, OAuth credentials) per platform. - Migration & Verification Workflow: A 4-step process covering pre-deployment checks, Prisma migration strategy (including the constraint that the runtime image has no Prisma CLI), and post-deployment verification via /api/health. - Use Case: You want to move your Resparkable app from local development to Railway with a managed PostgreSQL database. The Skill provides the exact railway.json, environment variable references, and migration command sequence. ## Quick Start Ask the assistant to generate a deployment guide for deploying this project to Vercel with a Neon PostgreSQL database.

Frequently Asked Questions about deployment-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js app with Prisma to Vercel?▼

Import the repository in the Vercel dashboard, set environment variables including DATABASE_URL and BETTER_AUTH_SECRET, and use the build command 'prisma generate && prisma migrate deploy && npm run build'. Pair it with an external PostgreSQL provider such as Neon or Supabase.

What environment variables are required for production deployment?▼

Required variables are DATABASE_URL, BETTER_AUTH_SECRET (minimum 32 characters), BETTER_AUTH_URL, and NEXT_PUBLIC_APP_URL. Production email requires RESEND_API_KEY and EMAIL_FROM, while Google OAuth needs GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET.

Why do Prisma migrations fail in the deployed container?▼

The Sunrise runtime Docker image contains no Prisma CLI, so Render or Railway Pre-Deploy commands and Fly release_command fail when running migrate deploy. Run migrations from CI or a local checkout, or use the dedicated migrator image instead.

How do I run database migrations on Railway or Render?▼

Run 'npm run db:migrate:deploy' from a CI runner or local checkout with full node_modules, not inside the deployed container. For Vercel, append the migrate command to the build command so it executes during the build phase.

Why is login not working after deployment?▼

Authentication failures usually come from a BETTER_AUTH_URL that does not match the production domain or a BETTER_AUTH_SECRET shorter than 32 characters. Also verify cookies are being set in browser dev tools and that OAuth callback URLs match exactly.

How do I verify a deployment succeeded?▼

Visit /api/health and confirm it returns {"status":"ok"}, then test the signup and login flows. Additionally verify email sending, error tracking events, SSL, and any custom domain configuration.