What problem does it solve? Converting Svelte writable/readable/derived stores and $state/$derived runes into a Redux + redux-saga architecture is error-prone: reducers can become impure, side effects leak into components, and old store files linger as wrappers. This Skill provides an ordered, verifiable playbook for migrating one store at a time with cleanup evidence. ## Core Features & Use Cases - Assessment and classification: Inventory existing stores and runes, then classify each as shared Redux state versus component-local state using a decision framework. - Step-by-step conversion sub-skills: Dedicated guides for setup/bootstrap, writable stores, derived stores, side effects, component migration, and cleanup/rollback. - Verifier-ready evidence: Each step produces grep checks, tests, and cleanup reports proving zero residual references to old store paths. - Use Case: A team migrating a SvelteKit app from scattered .store.svelte.ts files to a centralized Themis Redux store uses this Skill to convert the cart store first, moving its localStorage sync into a saga and its derived totals into selectors. ## Quick Start Ask the AI to assess the Svelte stores in src/lib/stores and produce a migration plan converting them to Redux slices and sagas one at a time.
