Cloudflare Deploy

Cloudflare Deploy

Use this skill to choose the correct Cloudflare product, inspect the project or infrastructure shape, and then load only the relevant reference folder before making changes or deploying.

Prerequisites

• The current environment can run terminal commands when needed.
• The user has access to the relevant Cloudflare account.
• The required Cloudflare toolchain is available for the selected workflow, usually wrangler via npx wrangler.

If authentication or CLI setup is not ready, read references/setup.md before continuing.

Required Workflow

Follow these steps in order:

Step 1: Identify the Cloudflare product first

Do not jump straight to deployment commands. First decide which product matches the request:

• workers for edge code execution
• pages for web app hosting
• durable-objects, kv, d1, r2, queues, or vectorize for data and state
• workers-ai, agents-sdk, ai-gateway, or ai-search for AI features
• waf, turnstile, api-shield, or bot-management for security
• tunnel, spectrum, turn, argo-smart-routing, or related networking tools for connectivity

Use the decision trees below for quick routing, then load only the needed reference directory instead of scanning the entire references/ tree.

Step 2: Inspect the local project or target infrastructure

Before changing anything, inspect the relevant files and deployment shape:

• For application deploys: check package.json, wrangler.jsonc, wrangler.toml, netlify.toml alternatives if migrating, build scripts, lockfiles, and framework config.
• For Pages: determine the build command and output directory.
• For Workers: determine the entrypoint, bindings, compatibility date, routes, and environments.
• For infrastructure or security tasks: confirm the target account, zone, resource identifiers, and environment.

Step 3: Verify authentication and tool readiness

Verify auth before wrangler deploy, wrangler pages deploy, or other Cloudflare CLI operations:

npx wrangler whoami    # Shows account if authenticated

If authentication is missing, stop and use references/setup.md. Do not guess credentials, account IDs, or zone IDs.

Step 4: Load only the matching reference set

After selecting the product, read the relevant reference folder:

• Start with that folder's README.md
• Then load configuration.md, api.md, patterns.md, or gotchas.md only if needed
• Avoid loading unrelated product references

Quick Decision Trees

"I need to run code"

Need to run code?
├─ Serverless functions at the edge → workers/
├─ Full-stack web app with Git deploys → pages/
├─ Stateful coordination/real-time → durable-objects/
├─ Long-running multi-step jobs → workflows/
├─ Run containers → containers/
├─ Multi-tenant (customers deploy code) → workers-for-platforms/
├─ Scheduled tasks (cron) → cron-triggers/
├─ Lightweight edge logic (modify HTTP) → snippets/
├─ Process Worker execution events (logs/observability) → tail-workers/
└─ Optimize latency to backend infrastructure → smart-placement/

"I need to store data"

Need storage?
├─ Key-value (config, sessions, cache) → kv/
├─ Relational SQL → d1/ (SQLite) or hyperdrive/ (existing Postgres/MySQL)
├─ Object/file storage (S3-compatible) → r2/
├─ Message queue (async processing) → queues/
├─ Vector embeddings (AI/semantic search) → vectorize/
├─ Strongly-consistent per-entity state → durable-objects/ (DO storage)
├─ Secrets management → secrets-store/
├─ Streaming ETL to R2 → pipelines/
└─ Persistent cache (long-term retention) → cache-reserve/

"I need AI/ML"

Need AI?
├─ Run inference (LLMs, embeddings, images) → workers-ai/
├─ Vector database for RAG/search → vectorize/
├─ Build stateful AI agents → agents-sdk/
├─ Gateway for any AI provider (caching, routing) → ai-gateway/
└─ AI-powered search widget → ai-search/

"I need networking/connectivity"

Need networking?
├─ Expose local service to internet → tunnel/
├─ TCP/UDP proxy (non-HTTP) → spectrum/
├─ WebRTC TURN server → turn/
├─ Private network connectivity → network-interconnect/
├─ Optimize routing → argo-smart-routing/
├─ Optimize latency to backend (not user) → smart-placement/
└─ Real-time video/audio → realtimekit/ or realtime-sfu/

"I need security"

Need security?
├─ Web Application Firewall → waf/
├─ DDoS protection → ddos/
├─ Bot detection/management → bot-management/
├─ API protection → api-shield/
├─ CAPTCHA alternative → turnstile/
└─ Credential leak detection → waf/ (managed ruleset)

"I need media/content"

Need media?
├─ Image optimization/transformation → images/
├─ Video streaming/encoding → stream/
├─ Browser automation/screenshots → browser-rendering/
└─ Third-party script management → zaraz/

"I need infrastructure-as-code"

Need IaC? → pulumi/ (Pulumi), terraform/ (Terraform), or api/ (REST API)

Product Index

Compute & Runtime

Storage & Data

AI & Machine Learning

Networking & Connectivity

Security

Media & Content

Real-Time Communication

Developer Tools

Infrastructure as Code

Other Services

Troubleshooting

Network Access

If Cloudflare CLI operations fail due to DNS or outbound network restrictions, rerun them with the host's elevated or unrestricted network mode when available.

Authentication Problems

Use references/setup.md and references/wrangler/auth.md when:

• npx wrangler whoami fails
• the account is wrong
• token-based auth is needed for CI or headless environments

Scope Problems

If the request is broad, narrow it before acting:

• which Cloudflare product
• which account or zone
• which environment
• whether the task is read-only, configuration, migration, or deployment