メニュー
Apply Cloudflare reference architecture patterns for CRUD SaaS, collaboration, async exports, AI assistants, RAG, media, webhook ingestion, and migration. Use to turn requirements into an implementation pattern and primitive map.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | patterns |
| description | Apply Cloudflare reference architecture patterns for CRUD SaaS, collaboration, async exports, AI assistants, RAG, media, webhook ingestion, and migration. Use to turn requirements into an implementation pattern and primitive map. |
| compatibility | Cloudflare Workers TypeScript projects using Wrangler; verify current Cloudflare APIs, limits, and pricing before production use. |
| metadata | {"source":"Architecting on Cloudflare plus official Cloudflare Developer Platform docs","generated":"2026-04-28"} |
Use this skill when a user describes an application and needs a Cloudflare implementation shape.
Worker: API, auth, SSR/static assets
D1: tenants, users, records, permissions
R2: file uploads
KV: cached public/config reads
Queue: email/webhook/export jobs
Observability: request IDs and tenant IDs
Add Durable Objects only when a specific entity needs serialized coordination.
Worker: auth and WebSocket upgrade route
Durable Object per room/document: live state, message ordering, presence
D1: metadata, membership, audit/history summaries
R2: snapshots, exports, attachments
Queue: indexing, notifications, compaction
Key by tenant:{tenantId}:doc:{docId} or similar.
Worker: validate request, create job record, enqueue/start workflow
Workflow: durable ordered steps, retries, progress
D1: job status and metadata
R2: generated report
Queue: fan-out chunks when needed
Return HTTP 202 with jobId; expose a status endpoint.
Worker: upload/query APIs and auth
R2: original documents and parsed chunks
D1: document metadata, ACL, ingestion status
Workflow/Queue: parse, chunk, embed, index
Vectorize or AI Search: retrieval index
Workers AI / AI Gateway: embeddings and answer generation
Ensure retrieval filters enforce tenant/user authorization.
Worker: auth, upload/download routing
R2: original and transformed media
D1: metadata, ownership, processing state
Queue/Workflow: transformations, notifications
Container: only if native/heavy processing is required
Realtime/WebRTC: only for live media sessions
Worker: verify signature, store minimal event, enqueue
Queue: process retries/idempotency
D1: event ledger and domain records
Durable Object: only if events must serialize by account/entity
Build Cloudflare Agents SDK applications for autonomous multi-step tool use, AIChatAgent chat agents, Durable Object-backed state, tools, scheduling, callable methods, WebSockets, SQL state, and constrained agent behavior. Use when RAG or Workflows are not enough.
Choose Cloudflare Developer Platform primitives and architecture shapes before writing code. Use for Cloudflare Workers, Durable Objects, D1, R2, Queues, Workflows, Containers, Realtime, Workers AI, Vectorize, AI Search, Agents, cost, limits, and migration decisions.
Decide when to use Cloudflare Containers instead of Workers and design container-backed workloads, native binaries, long-running processes, image processing, larger runtime shapes, and Worker frontends. Use as an escape hatch when Workers constraints do not fit.
Optimize Cloudflare Developer Platform costs for Workers CPU vs wall time, D1 operations, KV reads/writes, R2 storage/egress, Durable Object hotspots, Queues, Workflows, Workers AI tokens, and architecture-level trade-offs. Use during design and production reviews.
Write Cloudflare D1 code and schemas for SQLite-backed relational data, prepared statements, bindings, migrations, typed queries, tenant boundaries, indexes, pagination, and idempotent writes. Use when Workers need SQL data on Cloudflare.
Build Cloudflare Durable Objects for stateful coordination, one-per-entity actors, strong consistency, private SQLite-backed storage, RPC methods, WebSockets, alarms, sessions, rooms, rate limits, and collaborative state. Use when Workers code needs serialized state or race-free coordination.