auto-svelte

Detect and fix SSR state leaks and unsafe reactivity in Svelte 5 code.

6|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill auto-svelte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-svelte
Source: https://github.com/Corvalis-LLC/Crow-Stack/tree/main/skills/auto-svelte
Command: npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill auto-svelte

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about auto-svelte

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

FAQPage Schema
How do I prevent SSR state leaks in Svelte 5 components?

Prevent SSR state leaks in Svelte 5 by auditing module-level state and enforcing per-request state isolation. Apply proper $state discipline and guardrails across components and routes to keep server-side rendering safe and predictable.

What is the correct way to use $state.raw and $state.snapshot in Svelte 5?

Use $state.raw for non-reactive plain values and $state.snapshot to capture immutable views of reactive state. These patterns ensure safe data handling and per-request isolation during Svelte 5 server-side rendering.

Why does module-level state cause unsafe reactivity in SvelteKit SSR?

Module-level state causes unsafe reactivity because it shares mutable data across all server requests, breaking per-request isolation in SvelteKit SSR and leading to leaked user data or unpredictable component behavior.

How do I audit svelte-ignore usage for per-line ignore pitfalls in Svelte 5?

Audit svelte-ignore usage by checking for one-line per-line ignore rules that suppress critical warnings across components and routes, ensuring they do not mask underlying SSR safety or reactivity issues in Svelte 5.

Can I use lucide-svelte with Svelte 5 without running into type quirks?

You can use lucide-svelte with Svelte 5, but you must address its type quirks during integration. Auditing these quirks alongside Buffer handling in SSR responses improves overall application reliability and rendering performance.