astro-islands
Expert Astro Islands Architecture — client:load, client:idle, client:visible, client:media, client:only, server:defer (Server Islands), fallback slots, transition:persist, prop serialization. Use when adding interactivity to Astro pages or rendering dynamic server content.
What this skill does
# Astro Islands Expert Partial hydration architecture: zero JS by default, selective interactivity via directives. ## Agent Workflow (MANDATORY) Before ANY implementation, use `TeamCreate` to spawn 3 agents: 1. **fuse-ai-pilot:explore-codebase** - Analyze existing components and hydration patterns 2. **fuse-ai-pilot:research-expert** - Verify latest Islands docs via Context7/Exa 3. **mcp__context7__query-docs** - Get client directive and server:defer examples After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview ### When to Use - Adding interactive React/Vue/Svelte/Solid components to Astro pages - Deferring dynamic server content without blocking page load - Persisting component state during View Transitions - Optimizing Time to Interactive with lazy hydration ### Why Islands Architecture | Concept | Benefit | |---------|---------| | Zero JS by default | Maximum performance, minimal payload | | Selective hydration | Only interactive components ship JS | | `server:defer` | Dynamic server content without SSR blocking | | `client:visible` | Lazy-load below-fold components | | `transition:persist` | State survives page navigation | --- ## Client Directives | Directive | When JS Loads | Use Case | |-----------|--------------|----------| | `client:load` | Immediately on page load | Critical interactive UI | | `client:idle` | After `requestIdleCallback` | Non-critical UI | | `client:visible` | When component enters viewport | Below-fold components | | `client:media="(query)"` | When media query matches | Responsive components | | `client:only="framework"` | Client-only, no SSR | Components using browser APIs | ## Server Islands `server:defer` renders the component on the server after the page loads: - Uses `slot="fallback"` for placeholder content - Ideal for personalized or auth-gated content - Does not block initial page render - Requires a server adapter --- ## Reference Guide | Need | Reference | |------|-----------| | Architecture overview | [overview.md](references/overview.md) | | Client directive details | [client-directives.md](references/client-directives.md) | | server:defer patterns | [server-islands.md](references/server-islands.md) | | transition:persist | [transitions.md](references/transitions.md) | | View Transitions (complete) | [view-transitions.md](references/view-transitions.md) | | Prop serialization rules | [prop-serialization.md](references/prop-serialization.md) | | Interactive component | [templates/interactive-island.md](references/templates/interactive-island.md) | | Server island with fallback | [templates/server-island.md](references/templates/server-island.md) | --- ## Best Practices 1. **Default to no directive** — Ship zero JS unless interactivity is required 2. **Prefer `client:visible`** — Defer below-fold components automatically 3. **`client:only` for browser APIs** — localStorage, window, canvas 4. **`server:defer` for personalized content** — Avatars, prices, auth state 5. **`transition:persist`** — Preserve media players or forms during navigation
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.