workers-best-practices

Check binding access patterns, handler signatures, and configuration against the project's installed types and Wrangler schema, then retrieve current Cloudflare docs for anything uncertain. Flag anti-patterns like buffered unbounded bodies, floating promises, and hardcoded secrets.

Common anti-patterns include awaiting response.text() on unbounded data, Math.random() for security tokens, module-level mutable request state, destructuring ctx methods, and using REST APIs instead of bindings. Each has a documented preferred pattern such as streaming or crypto.randomUUID().

Module export handlers like fetch, scheduled, and queue access bindings through the env parameter. Classes extending platform base classes such as WorkerEntrypoint, DurableObject, or Workflow access them through this.env.X instead.

Yes, setting observability.enabled to true alone does not enable traces. You must also set observability.traces.enabled to true, and use head_sampling_rate to control log and trace volume.

Destructuring ctx, such as const { waitUntil } = ctx, loses the receiver binding and throws Illegal invocation at runtime. Always call ctx.waitUntil(...) directly on the context object.

Durable Objects specifics belong to the dedicated durable-objects skill, Workflow rules are covered by the Rules of Workflows documentation, and Wrangler CLI command usage belongs to the wrangler skill. This Skill covers Workers-specific code and configuration review only.