michaelschecht cloudflare-deploy
Deploy applications and supporting infrastructure to Cloudflare using Workers, Pages, and related platform services.
Overview
Use this skill when:
- The user wants to deploy or host on Cloudflare
- A project targets Workers, Pages, KV, R2, D1, or Durable Objects
- You need to set up environment bindings or edge-friendly deployment config
- You are migrating a small app or API to Cloudflare's edge runtime
Workflow
- Identify the runtime target: Workers, Pages, or a hybrid setup.
- Confirm the build output, entrypoint, and required bindings.
- Configure environment variables, secrets, and resource bindings explicitly.
- Validate local build output before deployment.
- Deploy to preview or staging first when possible.
- Verify routes, logs, and edge-runtime compatibility after release.
Deployment Checklist
- Entry file and runtime mode are correct
- Build command and output directory are explicit
- Secrets are stored as Cloudflare secrets, not plain config
- KV, D1, R2, Durable Objects, and queues are declared intentionally
- Custom domains and routes are mapped to the correct environment
Common Concerns
Workers
- Check runtime API compatibility
- Avoid unsupported Node assumptions unless compatibility mode is enabled
- Keep startup and dependency weight small
Pages
- Confirm static build output path
- Separate framework build concerns from deployment config
- Verify edge functions only where needed
Guardrails
- Do not assume a Node server can be deployed unchanged to Workers
- Avoid mixing production secrets into preview environments
- Verify database and storage bindings per environment
- Treat edge-runtime limitations as design constraints, not incidental bugs