A locally working app, deployment target, required environment names, and rollback plan.
A deployed app that completes its main journey with the correct environment and a known rollback path.
Check the actual deployed URL and persistence/authentication paths; confirm the rollback target without running a production migration.
A finished deploy is not the same as a working app: missing environment values, the wrong build folder or data that vanishes on redeploy show up only when someone uses it. This skill guides your coding agent from a working build to a verified live app on Vercel or Railway, from prerequisites to a checked result.
Your agent runs the production build and its checks locally, prepares the host using the actual repository build context, and compares environment variable names with the app's example file. Secrets go in the host's environment settings, and server credentials stay out of public variables.
On a preview deployment it checks the main journey and a failure case, persistence and external service access, and reads the runtime logs. You record the deployment identity and a rollback target, and promote only the version that passed the preview check.
You need a working production build, a hosting account and the environment values the app requires. Hosting and provider charges are separate; provider accounts, model weights, GPU compute and hosting are not included.
No reviews yet.
Sign in to rate this Vibe.
Go from a vague request to a repair you can show working, with a brief, a failing check, a passing check and a handoff on record.