vinext-cloudflare-hardening

Run the inspect-vinext-cloudflare.sh helper against your repo to inventory Wrangler config, bindings, and scripts, then review cache strategy, asset and image bindings, and environment handling. The skill writes a hardening plan to docs/cloudflare/ with findings and next steps.

Check that an assets binding exists when the Worker serves static assets, image handling is explicitly configured, and KV namespaces exist for any cache handler the app uses. The helper script scans wrangler.jsonc or wrangler.toml for these markers.

No. The skill first verifies the repo depends on vinext, has a vite.config file, and uses vinext dev, build, or deploy scripts. If the project is still on Next.js, it routes you to the migrate-to-vinext skill instead.

A successful dev start does not validate deployment config. Common causes include missing assets or KV bindings, cache handlers without backing bindings, and config drift between local, preview, and production Wrangler environments.

The script outputs text or JSON listing the repo path, vinext dependency presence, Wrangler and Vite config files, dev/build/deploy scripts, environment files, Wrangler binding markers, and files referencing bindings like KV, R2, or Durable Objects.