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 Enforcement: Checks Workers code against canonical rules covering streaming, waitUntil usage, bindings over REST APIs, Hyperdrive, observability, and Web Crypto security. - Type and Config Validation: Verifies Env binding types, handler signatures, wrangler.jsonc fields, compatibility dates, and binding-code consistency using retrieved schemas rather than guesswork. - 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, load this skill to validate the wrangler config, check binding access patterns, and catch floating promises before merge. ## Quick Start Review my Cloudflare Worker code and wrangler.jsonc for best-practice violations and common anti-patterns.