cloudflare

Guides Cloudflare platform development across Workers, storage, AI, networking, and security products.

Updated Nov 23, 2024
One-click install
npx skills add https://github.com/tokisakiyuu/dotfiles --skill cloudflare-tokisakiyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloudflare
Source: https://github.com/tokisakiyuu/dotfiles/tree/main/home/dot_claude/skills/cloudflare
Command: npx skills add https://github.com/tokisakiyuu/dotfiles --skill cloudflare-tokisakiyuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right Cloudflare product and writing correct code against its APIs is hard because the platform spans dozens of services with frequently changing limits, types, and configuration options. This Skill routes you to the right product via decision trees and provides detailed per-product references while biasing toward live documentation retrieval over stale pre-trained knowledge. ## Core Features & Use Cases - Product Decision Trees: Route requirements (run code, store data, AI/ML, networking, security, media, analytics, IaC) to the correct Cloudflare product and its reference docs. - Per-Product API References: Detailed guides for Workers, Pages, D1, KV, R2, Durable Objects, Workers AI, Vectorize, Terraform, Wrangler, and more, with TypeScript examples and gotchas. - Retrieval-First Guidance: Directs lookups to Cloudflare docs, workers-types packages, and Wrangler config schemas so numeric limits, pricing, and API signatures stay current. - Use Case: You need to add feature flags to a Workers app. The decision tree routes you to Flagship, and the reference shows binding setup (env.FLAGS), OpenFeature SDK usage, and REST API management. ## Quick Start Ask the AI which Cloudflare product fits your use case, for example how to store relational data or run scheduled jobs, and let it load the matching reference.

Frequently Asked Questions about cloudflare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Cloudflare Workers, Pages, and Durable Objects?▼

Use Workers for serverless functions at the edge, Pages for full-stack web apps with Git deploys, and Durable Objects for stateful coordination or real-time use cases. The skill's decision trees map each requirement to the right compute product.

What Cloudflare storage option should I use for my data?▼

Use KV for key-value config and sessions, D1 for relational SQLite, R2 for S3-compatible object storage, Queues for async messaging, and Vectorize for embeddings. Durable Object storage fits strongly-consistent per-entity state.

Can I manage Cloudflare resources with Terraform or Pulumi?▼

Yes, the skill includes Terraform and Pulumi references covering provider setup, data sources, resource naming changes between v4 and v5, and import ID formats for zones, DNS records, Workers, KV, R2, and D1.

Why should I verify Cloudflare limits and API signatures against live docs?▼

Cloudflare limits, pricing, types, and configuration options change frequently, so pre-trained knowledge may be outdated. The skill instructs retrieval from developers.cloudflare.com, @cloudflare/workers-types, and Wrangler's config schema before citing specifics.

How do I access Cloudflare Secrets Store from a Worker?▼

Secrets Store bindings require an async .get() call that throws on error rather than returning null, so always wrap it in try/catch. Secrets are not directly available as plain strings like regular Worker secrets.

When should I not use Cloudflare Snippets?▼

Snippets only support lightweight HTTP modification with fetch, Request, Response, and crypto APIs. They lack KV, D1, R2, Durable Objects, WebSocket, HTMLRewriter, and module imports, so use a full Worker for those needs.