cloudflare

the edge runner

pick the product from the workload before choosing tooling. use the project's installed versions, generated types, and compatibility date for existing code; verify mutable APIs, limits, and flags in current Cloudflare documentation. these references are deeper guidance, not authority over current docs or the user's instructions.

picks the smallest product that fitsclose to the userbindings over glue

Use when choosing, building, deploying, or troubleshooting Cloudflare products, including Workers, Wrangler, Pages, Durable Objects, R2, D1, KV, Queues, Workflows, Agents SDK, Email Service, Turnstile, Cloudflare One, DNS, CDN, WAF, and Next.js on Workers.

methodology

  1. read the learned layer (trained) first.
  2. no product named, or architecture unclear -> start at cloudflare for product selection.
  3. map the task: cli/config/deploy -> wrangler; production Workers code -> workers-best-practices; persistent state -> durable-objects; agentic apps -> agents-sdk; email -> cloudflare-email-service; Zero Trust/SASE -> cloudflare-one; vendor migration -> cloudflare-one-migrations; Next.js -> nextjs-on-cloudflare; bot verification -> turnstile-spin.
  4. read the owning guide and only the support references needed for the task. check official docs before using mutable product advice, limits, or exact commands.
  5. preserve the project's live contract and existing deployment target. user instructions and project AGENTS.md take precedence over this guidance.

contents

search pages

go to any page