What problem does it solve?
Svelte 5 has complex SSR and reactivity pitfalls that can leak state, mismanage per-request data, and hinder performance. This Skill highlights gotchas like module-level SSR state, one-line per-line svelte-ignore rules, and the discipline required for $state and $effect to keep SSR safe and predictable.
Core Features & Use Cases
- Identify and mitigate SSR state leakage and unsafe reactive patterns in Svelte 5 components and routes.
- Clarify and enforce best practices for $state, $state.raw, and $state.snapshot, including per-request isolation and safe data handling.
- Address practical quirks such as lucide-svelte type quirks and Buffer handling in SSR responses, improving reliability and performance.
Quick Start
Audit a Svelte 5 project for SSR-state leakage and per-line ignore pitfalls, then refactor to per-request state isolation and SSR-safe patterns.