What problem does it solve? Cloudflare Workers code often breaks due to stale API signatures, wrong binding access patterns, floating promises, secrets in config, or outdated compatibility dates. This Skill grounds implementation and review work in the current Workers runtime types, Wrangler schema, and documented best practices so changes are verified rather than assumed. ## Core Features & Use Cases - Implementation guidance: Applies rules for streaming, waitUntil, request isolation, secrets management, bindings, Queues, Workflows, Hyperdrive, and observability when writing Workers code. - Structured code review: Checks type integrity (no any, no double-casting), binding access patterns (env.X vs this.env.X), wrangler config validity, serialization boundaries, and security issues, reporting findings with severity, file/line, and evidence. - Retrieval-first verification: Fetches the latest @cloudflare/workers-types and Wrangler config-schema.json instead of guessing API signatures or config fields. - Use Case: When adding a Queue binding to a Worker, use this Skill to verify the binding type, update wrangler.jsonc correctly, ensure messages are serializable, and confirm no floating promises remain in the handler. ## Quick Start Review my Cloudflare Worker code and wrangler config for best-practice violations and type errors.
