cloud-architecture-cloudflare

What problem does it solve?

Building on Cloudflare's unique edge platform requires specialized knowledge of its primitives, limits, and billing models that differ sharply from traditional cloud providers. Without this expertise, teams regularly hit unexpected CPU limits, consistency bugs, cost overruns, and architectural dead ends when designing or scaling Cloudflare-backed systems.

Core Features & Use Cases

• Comprehensive primitive guidance: Detailed breakdowns of all core Cloudflare edge services (Workers, R2, D1, KV, Durable Objects, Queues, Workers AI, Hyperdrive) including their consistency models, hard limits, and ideal use cases.
• Pitfall prevention: Explicit documentation of common failure modes (e.g., Exceeded CPU errors, KV stale reads, Durable Object hot bottlenecks) with clear steps to diagnose and avoid them.
• Cost optimization insights: Cloudflare-specific billing guidance (no R2 egress, CPU-time billing for Workers, D1 rows-based billing) to help teams minimize spend on edge workloads.
• Use case example: A team building a global real-time collaboration app can use this skill to select Durable Objects for WebSocket coordination instead of KV to avoid stale state, and pair Workers with Smart Placement and Hyperdrive to reduce origin latency for their Postgres backend.

Quick Start

Use the cloud-architecture-cloudflare skill to design a scalable, cost-effective Cloudflare edge architecture for your new global SaaS application, including guidance on selecting the right storage primitives and avoiding common platform limit pitfalls.