plugins/astro-expert/skills/astro-deployment/SKILL.md
Deploying Astro 7 apps — @astrojs/cloudflare (Workers, D1, KV, R2), @astrojs/vercel (Serverless/Edge, Image CDN), @astrojs/netlify (Edge Functions), @astrojs/node (standalone), ISR patterns, edge middleware, skew protection. Use for any deployment configuration.
npx skillsauth add fusengine/agents astro-deploymentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Production deployment for Astro 7 across all major platforms — Cloudflare, Vercel, Netlify, and Node.js.
Before ANY implementation, use TeamCreate to spawn 3 agents:
After implementation, run fuse-ai-pilot:sniper for validation.
| Platform | Package | Runtime | Notes |
|----------|---------|---------|-------|
| Cloudflare | @astrojs/cloudflare v13+ | workerd | Astro 6: astro dev runs on workerd |
| Vercel | @astrojs/vercel | Node/Edge | Image CDN built-in |
| Netlify | @astrojs/netlify | Edge | Deno-based edge functions |
| Node.js | @astrojs/node | Node | Standalone server mode |
output: 'static' — Full SSG, no adapter neededoutput: 'server' — Full SSR, adapter requiredexport const prerender = true/falseAstro 6 runs astro dev on workerd — same runtime as production. Enables D1, KV, R2 bindings in local dev via platformProxy. No more simulation gaps. Requires @astrojs/cloudflare v13+ and Node.js 22+.
Astro has no native ISR. Implement with platform caching: Cloudflare KV as cache layer, or Vercel's Cache-Control with stale-while-revalidate.
On Vercel, enable skew protection to prevent asset mismatches between old client and new server during deployments.
| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Cloudflare | cloudflare-adapter.md | Workers, D1, KV, R2, wrangler | | Vercel | vercel-adapter.md | Serverless, Edge, Image CDN | | Netlify | netlify-adapter.md | Edge Functions, forms | | Node.js | node-adapter.md | Standalone, Express integration | | ISR Patterns | isr-patterns.md | Cache strategies, revalidation | | Edge Middleware | edge-middleware.md | Auth, redirects, A/B testing |
| Template | When to Use | |----------|-------------| | cloudflare-setup.md | Full Cloudflare config with bindings | | vercel-setup.md | Vercel config with Edge/Image CDN |
testing
Copy self-audit and ban-lists — filler verbs/hype adjectives, slop placeholder names, fake-precise numbers, Title Case headlines, humor in error copy ('Oops!'), em-dash crutch, one copy register per page.
development
Logged-in web apps — dashboards, auth flows, settings, onboarding, data tables, command palettes, modals, toasts. Register `product`: density and glance-speed over marketing polish, no hero/CTA-tricks, every data surface covers empty/loading/error explicitly, tables and dataviz follow preattentive-processing rules.
development
Marketing sites, landing pages, campaign pages — register `brand` (design IS the product). Structure comes from the register's POV + a macrostructure pick, never from copying an inspiration site's section flow. Hero discipline, deviated section order, asymmetric grids, and a silhouette lookalike-test gate before ship.
development
Token-strategy core — OKLCH color rules, neutral tinting, accent-commitment levels, type scale, 8pt spacing grid, touch targets, and the canonical output format of design-system.md (the file the harness gates on). This is routing step 1 of design-method/SKILL.md — read it before design-web/design-webapp/design-ios/design-android, before picking or auditing a single color/type/spacing value.