astro

Architect Astro islands projects to minimize client-side JavaScript.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill astro-dotbeeps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: astro
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/astro
Command: npx skills add https://github.com/dotBeeps/pantry --skill astro-dotbeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams adopt Astro's islands architecture and static-first rendering to reduce client-side JS and improve performance.

Core Features & Use Cases

  • Islands architecture — ship zero JS by default, hydrate only interactive components
  • Server-first rendering; use client:* directives only when client-side interactivity is needed
  • Static output by default — opt routes into SSR with prerender settings

Quick Start

Create a new Astro project configured for islands routing and place content in src/content to begin.

Frequently Asked Questions about astro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I minimize client-side JavaScript in web applications?

To minimize client-side JavaScript, use Astro's islands architecture to ship zero JS by default and hydrate only interactive components using client:* directives. This server-first rendering approach ensures static output unless specific routes opt into SSR.

What is islands architecture in frontend development?

Islands architecture is a frontend design pattern where pages ship zero JavaScript by default. Interactive components are treated as isolated islands that hydrate independently only when needed, using client directives to control client-side behavior.

How do I configure static output with selective SSR routes in Astro?

Configure static output by default and opt specific routes into server-side rendering using prerender settings. This allows content-driven routes to remain static while dynamic pages use SSR within the same project.

When should I use server-first rendering over client-side hydration?

Use server-first rendering for content-driven routes and modular UI components to reduce client-side JS. Apply client:* directives only when client-side interactivity is strictly needed, keeping the default output static.

Does Astro work for content-driven web applications requiring modular components?

Yes, Astro is built for content-driven web applications requiring modular components. It uses frontmatter-driven configuration and server directives to enable islands architecture, delivering fast, component-based UI with minimal client-side overhead.

How do I start building a project with Astro islands routing?

Create a new Astro project configured for islands routing, then place your content in the src/content directory to begin. Apply server directives during component development to manage hydration and static output.