@cloudflare

workers-best-practices validates cloudflare workers code against 40+ production rules, flags 15+ anti-patterns, and retrieves live api definitions and wrangler schemas to avoid stale knowledge.

web-perf audits core web vitals and render-blocking resources via chrome devtools mcp. detects layout shifts, network chains, caching gaps, and accessibility issues with checklist-driven prioritization.

cloudflare-browser exposes CDP control over WebSocket to headless Chrome in Cloudflare Workers, enabling screenshots, navigation, scraping, and video capture. requires manual worker setup and environment configuration.

cloudflare-one-migrations maps policies and objects from zscaler, palo alto, legacy vpn/swg stacks into cloudflare one equivalents, with inventory buildup, dependency sequencing, and staged rollout guidance.

turnstile-spin orchestrates end-to-end cloudflare turnstile integration by reading codebases, provisioning widgets via api, deploying siteverify workers, and inserting frontend snippets with validation confirmation.

durable-objects covers cloudflare's persistent edge coordination layer via state management, rpc methods, and deterministic routing, with sqlite and kv storage. useful for real-time sync patterns but procedural depth is limited.

sandbox-sdk provides isolated code execution on cloudflare workers with npm package setup and docker dependency. documentation is sparse and lacks actionable procedural depth.

building-ai-agent-on-cloudflare covers stateful ai agents on cloudflare workers using the agents sdk, with websocket communication, durable objects for persistence, and scheduled background tasks via cron or delay.

agents-sdk enables stateful ai agent construction on cloudflare workers via sqlite state management, rpc methods, task scheduling, and mcp server integration, with client-side react hooks for websocket communication.

guidance on deploying mcp servers to cloudflare workers with pointer to external docs. lacks procedural depth and concrete implementation examples.

cloudflare-email-service describes sending transactional emails and email routing via cloudflare, but the documentation is incomplete - it declares itself a convenience guide that lags behind api reality and defers actual procedural instruction to external sources.

Security audit of a codebase — web apps, APIs, services, CLI tools, libraries, daemons, and more. Use when asked to find security bugs, do a security review,…

Migrates Next.js projects to vinext (Vite-based Next.js reimplementation). Load when asked to migrate, convert, or switch from Next.js to vinext. Handles…

Use when porting a Cloudflare Sandbox app from stable @cloudflare/sandbox to @cloudflare/sandbox@next (Sandbox SDK 1.0 preview), or when the user asks to…

Use when building or changing Cloudflare Sandbox apps on @cloudflare/sandbox@next (Sandbox SDK 1.0 preview)—code execution, AI runners, interpreters, CI-like…

Use when building or changing Cloudflare Sandbox apps on the current stable @cloudflare/sandbox package (default npm tag)—commands, sessions, files, ports,…

Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when…

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows,…

Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship),…

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices.

Builds remote MCP (Model Context Protocol) servers on Cloudflare Workers with tools, OAuth authentication, and production deployment. Generates server code, configures auth providers, and deploys to Workers. Use when: user wants to "build MCP server", "create MCP tools", "remote MCP", "deploy MCP", add "OAuth to MCP", or mentions Model Context Protocol on Cloudflare. Also triggers on "MCP authentication" or "MCP deployment".

Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs.

Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task.

Builds AI agents on Cloudflare using the Agents SDK with state management, real-time WebSockets, scheduled tasks, tool integration, and chat capabilities. Generates production-ready agent code deployed to Workers. Use when: user wants to "build an agent", "AI agent", "chat agent", "stateful agent", mentions "Agents SDK", needs "real-time AI", "WebSocket AI", or asks about agent "state management", "scheduled tasks", or "tool calling".

Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks.

Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (FCP, LCP, TBT, CLS, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.

Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest.

Use when writing or running tests for this project. Covers unit vs E2E test decisions, test file locations, mock patterns, and project-specific testing conventions. (project)

Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.

Use when working on or reviewing session execution, command handling, shell state, FIFO-based streaming, or stdout/stderr separation. Relevant for session.ts, command handlers, exec/execStream, or anything involving shell process management. (project)