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 incorrect binding access that cause runtime failures or security issues. ## Core Features & Use Cases - Best-Practice Rule Enforcement: Applies canonical rules for configuration, streaming, waitUntil, bindings, observability, and Web Crypto security, with retrieval from live Cloudflare docs preferred over pre-trained knowledge. - Structured Code Review Workflow: Runs an eight-step review covering type validation, wrangler.jsonc config validation, binding-code consistency, serialization boundaries, and severity-rated findings with evidence and suggested fixes. - Anti-Pattern Detection: Flags common mistakes such as await response.text() on unbounded data, Math.random() for tokens, destructured ctx, hand-written Env interfaces, and implements instead of extends on platform base classes. - Use Case: When writing a new Worker with KV and Queue bindings, use this Skill to generate correct handler signatures, validate the wrangler config, and verify every Promise is awaited or passed to ctx.waitUntil() before deployment. ## Quick Start Review my Cloudflare Worker code and wrangler.jsonc for best-practice violations and anti-patterns.
