agentsclimarketplace

Astro deployment

Skill fusengine/agents/plugins/astro-expert/skills/astro-deployment

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.From its SKILL.md

Install
npx -y skills add fusengine/agents --skill astro-deployment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 3 commands, including `TeamCreate` and 2 more.

SKILL.md

4.0 KB, 896 tokens by cl100k_base, as published. Nobody here has run it

Astro Deployment

Production deployment for Astro 7 across all major platforms — Cloudflare, Vercel, Netlify, and Node.js.

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

  1. fuse-ai-pilot:explore-codebase - Analyze astro.config.mjs, output mode, and existing adapter
  2. fuse-ai-pilot:research-expert - Verify adapter docs via Context7/Exa for target platform
  3. mcp__context7__query-docs - Check Astro 7 adapter compatibility and breaking changes

After implementation, run fuse-ai-pilot:sniper for validation.


Overview

When to Use

  • Deploying Astro to Cloudflare Workers with D1/KV/R2 bindings
  • Configuring Vercel Serverless or Edge runtime with image CDN
  • Setting up Netlify Edge Functions
  • Running Astro as standalone Node.js server
  • Implementing ISR (Incremental Static Regeneration) patterns
  • Configuring edge middleware for auth/redirects

Adapter Matrix

PlatformPackageRuntimeNotes
Cloudflare@astrojs/cloudflare v13+workerdAstro 6: astro dev runs on workerd
Vercel@astrojs/vercelNode/EdgeImage CDN built-in
Netlify@astrojs/netlifyEdgeDeno-based edge functions
Node.js@astrojs/nodeNodeStandalone server mode

Core Concepts

Output Modes

  • output: 'static' — Full SSG, no adapter needed
  • output: 'server' — Full SSR, adapter required
  • Per-page: Mix with export const prerender = true/false

Cloudflare Astro

Astro 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+.

ISR Pattern

Astro has no native ISR. Implement with platform caching: Cloudflare KV as cache layer, or Vercel's Cache-Control with stale-while-revalidate.

Skew Protection

On Vercel, enable skew protection to prevent asset mismatches between old client and new server during deployments.


Reference Guide

Concepts

TopicReferenceWhen to Consult
Cloudflarecloudflare-adapter.mdWorkers, D1, KV, R2, wrangler
Vercelvercel-adapter.mdServerless, Edge, Image CDN
Netlifynetlify-adapter.mdEdge Functions, forms
Node.jsnode-adapter.mdStandalone, Express integration
ISR Patternsisr-patterns.mdCache strategies, revalidation
Edge Middlewareedge-middleware.mdAuth, redirects, A/B testing

Templates

TemplateWhen to Use
cloudflare-setup.mdFull Cloudflare config with bindings
vercel-setup.mdVercel config with Edge/Image CDN

Best Practices

  1. Match adapter to platform early - Switching adapters mid-project is painful
  2. Cloudflare: use v13+ for Astro 7 - Required for workerd local dev
  3. Node.js 22+ for Astro 7 - Drops Node 18/20 support
  4. Per-page prerender - Mix static and SSR for optimal performance
  5. Test bindings locally - Cloudflare platformProxy enables local D1/KV/R2

What ships with it: 8 files

14.8 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.