leptos-islands

Define hydration boundaries for Leptos SSR apps with islands.

Updated May 26, 2026
One-click install
npx skills add https://github.com/adelabdelgawad/rust-fullstack-agents --skill leptos-islands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: leptos-islands
Source: https://github.com/adelabdelgawad/rust-fullstack-agents/tree/main/plugins/rusty/skills/leptos-islands
Command: npx skills add https://github.com/adelabdelgawad/rust-fullstack-agents --skill leptos-islands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leptos Islands guide and enforces correct hydration boundaries to optimize SSR apps, ensuring interactive islands stay isolated from server-rendered content.

Core Features & Use Cases

  • Guidance on when to apply #[island] vs #[component] boundaries to minimize WASM footprint.
  • Patterns for modal, sheet, and tab interactions that keep flows within a single island.
  • Coordination strategies across islands (URL state, server actions, SSE) to share truth without crossing boundaries.

Quick Start

Plan and implement a small island in a sample page to validate hydration behavior.

Frequently Asked Questions about leptos-islands

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

FAQPage Schema
How do I define hydration boundaries in Leptos SSR apps to isolate interactive code?

To define hydration boundaries in Leptos SSR apps, use the #[island] macro to isolate interactive components from server-rendered content, preventing WASM leakage into static shells.

When should I use #[island] vs #[component] in Leptos to minimize WASM footprint?

Use #[island] for dynamic elements like modals, sheets, and forms requiring interactivity, and #[component] for static server-rendered content. Applying islands only to interactive boundaries minimizes the WebAssembly payload shipped to the client.

Can I use Leptos islands for admin dashboards and CRUD interfaces with mixed static and dynamic content?

Yes, Leptos islands are specifically applicable to admin dashboards and CRUD interfaces. They effectively mix static server-rendered shells with dynamic islands, modals, and forms while keeping interactive code isolated from server-rendered components.

What Leptos version is required to enable islands and manage hydration boundaries?

Leptos 0.8 is required to enable islands and manage hydration boundaries. This version enforces that signals and server actions stay within a single island subtree to maintain correct SSR hydration behavior.

How do you coordinate state across multiple Leptos islands without crossing hydration boundaries?

Coordinate state across multiple Leptos islands using URL state, server actions, and Server-Sent Events (SSE). These strategies share truth across islands without crossing hydration boundaries or leaking interactive code into server-rendered components.