What problem does it solve? Setting up and shipping an Appflare backend on Cloudflare Workers involves many moving parts: writing appflare.config.ts, creating D1/KV/R2/Queue resources, running migrations, managing secrets, and deploying with Wrangler. This Skill guides an AI agent through the entire lifecycle so configuration errors, stale migrations, and deploy mistakes are avoided. ## Core Features & Use Cases - Configuration authoring: Write and validate appflare.config.ts covering D1 databases with query limits, KV namespaces, R2 buckets, Better Auth options, scheduler queues, realtime Durable Objects, and wranglerOverrides. - CLI workflow: Run Bun CLI commands such as dev, dev --watch, build --no-build, migrate --local/--remote/--preview, migrate:custom for hand-written SQL migrations, and add-admin for creating admin users. - Deployment checklist: Follow production steps including wrangler secret put for BETTER_AUTH_SECRET, ALLOWED_DOMAINS CORS configuration, and wrangler deploy. - Use Case: You are starting a new Appflare project and need to create Cloudflare resources, wire up the config with real resource IDs, run the first local migration, and then ship to production with secrets and CORS locked down. ## Quick Start Ask the agent to set up a new Appflare backend on Cloudflare Workers, generate the config and wrangler bindings, run the local migration, and deploy it to production.