prepare-cloudflare-production-deployment

Prepare Cloudflare Production

Overview

Use this skill as the source of truth for production deployment. Cloudflare MCP must be used for Cloudflare account/resource discovery, verification, and supported mutations before using Wrangler, raw API calls, dashboard instructions, or assumptions. Use gh for GitHub repository secrets/variables; edit repo files directly for project branding, wrangler.jsonc, and workflow changes.

Never print secret values. Ask for missing secret values instead of inventing placeholders, and confirm before creating paid, destructive, or externally visible resources.

Preflight

1. Read wrangler.jsonc, package.json, .github/workflows/deploy.yml, src/constants.ts, src/utils/root-metadata.ts, src/components/footer.tsx, AGENTS.md, and cms.config.ts when relevant.
2. Check GitHub auth, then complete the MCP availability gate before any Cloudflare mutation:

gh auth status
gh repo view --json nameWithOwner,url

Report the Cloudflare account id/name/email from MCP and the GitHub account/repository from gh, then ask whether both are correct. Stop if the user says either account is wrong.

1. Confirm or remind the user about the required production customization checklist:
   • src/constants.ts has project details.
   • Read SITE_URL from src/constants.ts, derive the hostname, and check the domains/zones available in the authenticated Cloudflare account. Tell the user which matching or closest Cloudflare zone/domain was found and ask them to confirm it before proceeding. If the SITE_URL domain is not available in Cloudflare, stop and ask the user which Cloudflare zone/domain to use or whether they need to add the domain to Cloudflare first.
   • When the app will use Cloudflare Images, verify Images against that same production zone/hostname, not only against the account. Confirm the SITE_URL hostname belongs to a Cloudflare zone in the authenticated account and is proxied or attached as the Worker custom domain/route that production will use. Then verify the account-level Images API works for that account with /accounts/{account_id}/images/v1/variants or /accounts/{account_id}/images/v1/stats. If custom-domain image delivery is expected, explicitly confirm the production zone can serve Images URLs at https://<SITE_URL_HOSTNAME>/cdn-cgi/imagedelivery/<ACCOUNT_HASH>/<IMAGE_ID>/<VARIANT_NAME>; Cloudflare supports this only for customer domains under the same account as the Images account. If the domain is in a different account, not proxied through Cloudflare, or not the domain being deployed to, stop and ask which zone/domain should be used before proceeding.
   • Read package.json, tell the user the current name value, and ask them to confirm it is the intended production project name. This value controls generated deploy-size metrics and package metadata, so do not proceed if it still identifies the reused template. If the name is still cloudflare-workers-nextjs-saas-template, stop and ask the user for the real project name and production domain before editing Cloudflare resources, queue names, bindings, or deployment metadata.
   • Check queue names in wrangler.jsonc, especially queues.producers[].queue and queues.consumers[].queue. Queue names must be renamed to match the new production project name; do not leave template queue names such as cloudflare-workers-nextjs-saas-template-scheduler in a production project unless the user explicitly confirms that is the real project name.
   • Email Sending must follow the Email Sending procedure below: use the production SITE_URL zone, expect notifications.<SITE_URL_HOSTNAME>, and get user confirmation before Cloudflare or wrangler.jsonc changes.
   • AGENTS.md has the project specification for AI coding agents.
   • src/components/footer.tsx has project links and details.
   • src/app/globals.css color palette has been reviewed.
   • src/utils/root-metadata.ts metadata has project details; both root layouts read it.
   • The meta titles and descriptions in every locale catalog under src/i18n/messages/*.json (for example Client.Landing.meta, plus the auth, legal, and blog meta blocks) still default to template copy. Explicitly ask the user for the production titles and descriptions, and help them update these values in all locale catalogs, not only en.json.
   • cms.config.ts has been reviewed and updated if needed.