What problem does it solve? Cloudflare Workers APIs, types, and wrangler configuration change frequently, so code written from stale knowledge often contains anti-patterns like floating promises, global request state, hardcoded secrets, and misconfigured bindings that cause runtime failures or security issues. ## Core Features & Use Cases - Best-Practice Rule Enforcement: Checks configuration, streaming, waitUntil usage, bindings, observability, and security rules against the latest Cloudflare documentation. - Type and Config Validation: Verifies Env interfaces, handler signatures, binding access patterns, and wrangler.jsonc fields against current @cloudflare/workers-types and the wrangler config schema. - Anti-Pattern Detection: Flags issues like await response.text() on unbounded data, Math.random() for tokens, destructured ctx, and implements on platform base classes. - Use Case: When reviewing a pull request that adds a new Worker with KV bindings, use this Skill to validate the wrangler.jsonc config, confirm binding names match code, and flag any floating promises or missing nodejs_compat flags. ## Quick Start Review my Cloudflare Worker code and wrangler.jsonc for best-practice violations and common anti-patterns.