workers-best-practices

To review Cloudflare Workers code for production best practices, check handlers, bindings, and platform class usage for type correctness and anti-patterns. This skill analyzes your code to flag risky patterns like floating promises and global mutable state before deployment.

Common Cloudflare Workers anti-patterns include floating promises, global mutable state, weak randomness, and unsafe error handling. This skill helps identify these runtime pitfalls and ensures your handlers follow production reliability standards.

Validating wrangler configuration for Cloudflare Workers requires checking compatibility date, observability settings, secrets, and binding consistency. This skill reviews your wrangler config to catch outdated settings and ensure alignment with current Cloudflare APIs.

Yes, this Cloudflare Workers review checks type safety and runtime correctness by validating bindings, APIs, and platform classes against current Cloudflare type definitions. It flags broken binding access and type errors to ensure your code is production-ready.

The best way to check Cloudflare Workers observability and streaming configuration is to review your wrangler settings and handler logic for consistency. This skill validates your setup against current Cloudflare docs to ensure background work and streaming scenarios run correctly.

Your Cloudflare Worker may break when accessing bindings in production due to type mismatches or incorrect wrangler configuration. This skill reviews your binding access patterns and validates them against current type definitions to catch broken references before shipping.