What problem does it solve? Cloudflare Workers projects that depend on bindings like D1, KV, R2, Queues, Durable Objects, or Workflows often break or drift during local development because binding declarations, environment-specific config, and local-versus-remote assumptions are unclear. This Skill inventories the binding surface and turns it into a concrete local-dev plan. ## Core Features & Use Cases - Binding Inventory: Runs a helper script to detect wrangler.jsonc or wrangler.toml, env.* sections, .dev.vars files, and declarations for D1, KV, R2, Queues, Durable Objects, Workflows, and service bindings. - Environment Drift Detection: Verifies which bindings are declared at the top level versus per Wrangler environment, and flags code that references undeclared bindings or mixes process.env with runtime env access. - Local State Strategy: Documents whether D1/KV/R2/Queues should be simulated locally, where local state persists, and when remote bindings are genuinely required. - Use Case: A team whose Worker works in production but fails under wrangler dev can run this Skill to get a dated plan at docs/cloudflare/YYYY-MM-DD-bindings-local-dev.md covering bindings, environment model, and next steps. ## Quick Start Use the cloudflare-workers-bindings-local-dev skill to audit my project's Wrangler bindings and write a local development plan.
