wrangler_skill

Overview

This skill provides a concise, practical reference for using Wrangler, the Cloudflare Workers CLI for deploying, developing, and managing Workers and their associated resources. It focuses on correct configuration, common commands, and best practices to avoid deployment and runtime issues. Load it before running wrangler commands to ensure correct syntax and up-to-date guidance.

How this skill works

The skill inspects typical Wrangler workflows: project initialization, local development, configuration validation, deployment, and resource management (KV, R2, D1, Vectorize, Hyperdrive, AI, queues, containers, workflows, pipelines, and secrets store). It highlights config patterns (wrangler.jsonc), environment usage, binding options (including remote bindings), and CLI commands for each resource. Use it to validate syntax, generate types, and choose safe defaults for local vs. remote behavior.

When to use it

• Starting a new Cloudflare Workers project or scaffolding with a framework
• Preparing config before deployment or CI validation (wrangler check, wrangler types)
• Running local development and deciding between local simulation and remote bindings
• Managing cloud resources (KV, R2, D1, Vectorize, Hyperdrive, queues, containers)
• Creating, rotating, or bulk-managing secrets and secrets-store entries
• Deploying, rolling back, or inspecting observability logs and versions

Best practices

• Prefer wrangler.jsonc over TOML; newer features are JSON-only and schema-aware
• Keep compatibility_date current (within ~30 days) to avoid runtime regressions
• Run wrangler types after config changes and in CI with --check to keep TypeScript bindings accurate
• Validate config with wrangler check and use --dry-run for deployments to catch issues early
• Use env entries (staging/production) to separate settings and avoid accidental prod changes
• Use remote: true only for resources you need real state from (AI, Vectorize, Browser Rendering, Images)

Example use cases

• Initialize a new Worker and generate TypeScript types: npx wrangler init && wrangler types
• Run local development with simulated storage, then switch selected bindings to remote for integration testing
• Deploy a staging environment, validate with wrangler deploy --dry-run, then deploy to production
• Create and manage an R2 bucket and use wrangler r2 object put/get/delete for object ops
• Create a D1 database, run local migrations, and apply remote migrations when ready
• Manage secrets interactively or in bulk and bind them to the Worker via config