svelte5-runes-static

Bridge Svelte stores to Svelte 5 runes for hydration-safe static sites.

68|19|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill svelte5-runes-static
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: svelte5-runes-static
Source: https://github.com/bobmatnyc/claude-mpm-skills/tree/main/toolchains/javascript/frameworks/svelte5-runes-static
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill svelte5-runes-static

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenges of using Svelte 5 runes with SvelteKit's adapter-static (SSG/SSR) by providing patterns for hydration-safe state management, effective store bridging, and ensuring reactivity survives prerendering.

Core Features & Use Cases

  • Hydration-Safe State: Learn how to manage state that correctly hydrates after static site generation.
  • Store Bridging: Understand how to connect traditional Svelte stores to Svelte 5 runes.
  • Reactivity Patterns: Implement reactivity that works seamlessly with prerendering.
  • Use Case: When building a SvelteKit application with adapter-static, you encounter issues where component state becomes frozen after prerendering. This Skill provides the exact patterns to fix this by using traditional stores for global state and bridging them correctly to runes.

Quick Start

Use the svelte5-runes-static skill to implement hydration-safe state management for Svelte 5 runes in SvelteKit adapter-static projects.

Frequently Asked Questions about svelte5-runes-static

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

FAQPage Schema
Why does Svelte 5 runes state become frozen after prerendering with adapter-static?

Svelte 5 runes state becomes frozen after prerendering because adapter-static generates static HTML, causing component-local state to lose reactivity during hydration without proper store bridging patterns.

How do I bridge traditional Svelte stores to Svelte 5 runes in SvelteKit?

Bridge traditional Svelte stores to Svelte 5 runes by using global stores for persistent state and connecting them to component-local runes, ensuring reactivity survives prerendering and hydration in adapter-static projects.

Does SvelteKit adapter-static support Svelte 5 runes for SSG?

SvelteKit adapter-static supports Svelte 5 runes for SSG when applying specific hydration-safe state management patterns that maintain reactivity across prerendering and client-side hydration.

What's the best way to manage hydration-safe state with Svelte 5 runes?

The best way to manage hydration-safe state with Svelte 5 runes is a hybrid pattern using traditional Svelte stores for global state and bridging them correctly to component-local runes for adapter-static compatibility.

Can I use Svelte 5 runes reactivity patterns without losing prerendered state?

You can use Svelte 5 runes reactivity patterns without losing prerendered state by implementing recommended hybrid patterns that combine global stores with component-local runes to ensure reactivity persists across prerendering.