Migrate Astro from Webflow Cloud to Vercel

What this skill does

Moving an Astro app from Webflow Cloud to Vercel mostly means swapping the adapter, not rewriting the app. On Webflow Cloud the app runs as a Cloudflare Worker through the @astrojs/cloudflare adapter, served from a mount path inside a Webflow site. On Vercel the same app runs on Vercel Functions with Fluid compute on by default, in a full Node.js runtime, served from the root, so it scales with traffic on its own and supports Astro's full on-demand rendering feature set.

The app code (pages, components, Server Endpoints) mostly stays the same. The work sits in a few places: the Astro adapter and config, the Webflow Cloud and Wrangler config files that get deleted, the base path the app mounted under, the Edge runtime directive on API routes, and any server code that read storage bindings through locals.runtime.env.

The Vercel Plugin

The user will have installed the Vercel Plugin already, which among other things includes a number of helpful skills that can assist you and the user with this migration. Prefer those skills for current, detailed product guidance, and let this skill drive the order of work. The ones that line up with these steps:

• vercel-storage and marketplace: step 5 (Blob, Edge Config, Neon, Upstash, and Marketplace provisioning).
• env-vars: steps 5 and 6 (vercel env, .env files, OIDC tokens).
• vercel-cli and deployments-cicd: steps 6 and 7 (env vars and deploy).
• vercel-functions: step 5 (Server Endpoints on Vercel Functions) and the Best practices section (maxDuration, regions, ISR).

There are other skills included that may assist with the migration.