What problem does it solve? Deploying the PalFish GMV system involves two independently deployed components with non-obvious traps: Render auto-deploy is disabled despite render.yaml saying otherwise, tsc --noEmit gives false greens, and sandbox-to-production promotion requires a strict 4-step checklist. This Skill encodes the full deploy pipeline so nothing is missed. ## Core Features & Use Cases - Backend deploys to Render: Trigger manual deploys via bash scripts/deploy.sh [sandbox|prod] using gitignored deploy-hook URLs, then smoke-test /healthz to verify the correct Supabase project. - Frontend deploys to Vercel: Push to sandbox or main branch after the mandatory npx tsc -b TypeScript gate; handle the Preview-to-Production promotion gotcha. - Sandbox-to-production promotion: Follow the authoritative 4-step runbook covering pre-merge tests, Supabase prod migration with backup, merge and deploy, and post-deploy env var verification. - Use Case: You finished a sprint on the sandbox branch and need to ship to production. The Skill walks you through backend pytest, frontend tsc gate, DB migration with NOTIFY pgrst, 'reload schema', the merge, deploy.sh prod, and post-deploy checks including the USE_PAYOS log line and Chrome extension token update. ## Quick Start Ask the assistant to deploy the backend to sandbox and verify the healthz endpoint returns the correct Supabase project ref.