What problem does it solve? Migrating a Svelte application from stores and runes to Redux requires knowing exactly what state exists, who consumes it, and whether it belongs in shared Redux slices or component-local state. This Skill performs that assessment phase before any code is written, preventing overmigration and missed side effects. ## Core Features & Use Cases - Store Inventory: Searches the repository for writable, readable, derived, $state, $derived, and $effect usage and records findings as structured evidence. - State Classification: Applies a decision framework that routes shared, persisted, async, or business-logic state to Redux while keeping ephemeral UI state component-local. - Migration Planning Table: Produces a per-store table of state fields, derived values, side effects, consumers, and verdicts that downstream migration skills consume. - Use Case: Before migrating a cart feature, run the assessment to discover that cart.store.svelte.ts has localStorage sync and three consumers, yielding a Redux verdict routed to the writable-stores, derived-stores, and side-effects migration skills. ## Quick Start Audit the Svelte stores in src/ and produce a migration assessment table classifying each store as Redux or component-local.
