workers-best-practices

Your knowledge of Cloudflare Workers APIs, types, and configuration may be outdated. Prefer retrieval over pre-training for any Workers code task — writing or reviewing. Fetch the latest versions before writing or reviewing Workers code. Do not rely on baked-in knowledge for API signatures, config fields, or binding shapes. Before reviewing or writing Workers code, retrieve the current best practices page and relevant type definitions. If the project's node_modules has an older version, prefer the latest published version . This skill covers Workers-specific best practices and code review. For related topics: - references/rules.md — all best practice rules with code examples and anti-patterns - references/review.md — type validation, config validation, binding access patterns, review process - Retrieve — fetch latest best practices page, workers types, and wrangler schema - Read full files — not just diffs; context matters for binding access patterns - Check types — binding access, handler signatures, no any , no unsafe casts (see references/review.md ) - Check config — compatibility_date, nodejs_compat, observability, secrets, binding-code consistency - Check patterns — streaming, floating promises, global state, serialization boundaries - Check security — crypto usage, secret handling, timing-safe comparisons, error handling - Validate with tools — npx tsc --noEmit , lint...