What problem does it solve? Deploying an Astro application to production requires choosing and correctly configuring a platform adapter, output mode, caching strategy, and edge middleware — each with platform-specific quirks and version constraints that are easy to get wrong. ## Core Features & Use Cases - Adapter Configuration: Set up @astrojs/cloudflare (v13+, workerd runtime, D1/KV/R2 bindings via platformProxy), @astrojs/vercel (Serverless/Edge, Image CDN, skew protection), @astrojs/netlify (Deno Edge Functions), and @astrojs/node (standalone or Express middleware mode). - ISR Patterns: Implement incremental static regeneration using Vercel ISR options, Cloudflare KV caching, or Cache-Control: stale-while-revalidate headers, since Astro has no native ISR. - Edge Middleware: Build middleware for auth checks, geo-based redirects, and A/B testing using defineMiddleware and sequence. - Use Case: You need to deploy an Astro 7 site to Cloudflare Workers with a D1 database and KV cache — this Skill provides the wrangler.toml bindings, adapter config, and per-page prerender setup to do it correctly. ## Quick Start Ask the agent to configure your Astro project for deployment to Cloudflare Workers with D1 and KV bindings enabled in local dev.