svelte/migration/setup

Installs Themis dependencies and bootstraps a Redux store in a Svelte root layout before slice migration.

6|6|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/intent-hq/cloudlands-fe --skill svelte-migration-setup-intent-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: svelte/migration/setup
Source: https://github.com/intent-hq/cloudlands-fe/tree/main/.agents/skills/themis/svelte/migration/setup
Command: npx skills add https://github.com/intent-hq/cloudlands-fe --skill svelte-migration-setup-intent-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @augmentcode/themis, redux, redux-saga, typed-redux-saga, fast-equals.

What problem does it solve? Migrating Svelte stores to a Redux + redux-saga architecture fails without a correct foundation: missing peer dependencies, an uninitialized Store, or sagas started before init cause runtime errors. This Skill walks through the one-time pre-migration bootstrap so every subsequent slice migration starts from a working store. ## Core Features & Use Cases - Dependency Installation: Installs @augmentcode/themis with redux, redux-saga, typed-redux-saga, and fast-equals, plus the Svelte skill bundle via npx themis install-skills:svelte. - Store Bootstrap: Creates a single Store instance with an empty app-owned reducer map and StoreState<typeof store> type inference, initialized from the root +layout.svelte with proper disposal. - Saga Lifecycle Rules: Enforces correct ordering — store.init() before store.runSaga(sagaFn) — and prevents manually starting package-owned @internal_ sagas. - Use Case: A team migrating a SvelteKit app from writable()/derived() stores to Redux slices runs this setup once, then migrates slices one by one with reducers registered in the Store constructor map and sagas started from onMount. ## Quick Start Ask the AI to set up Themis in your SvelteKit project by installing the package and peers, creating src/lib/store/store.ts with an empty Store, and wiring store.init() into the root layout.

Frequently Asked Questions about svelte/migration/setup

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

FAQPage Schema
How do I set up Redux with redux-saga in a SvelteKit app?▼

Install @augmentcode/themis with redux, redux-saga, typed-redux-saga, and fast-equals, then create a single Store instance in src/lib/store/store.ts. Call store.init() in the root +layout.svelte and register the returned disposer with onDestroy.

How to migrate Svelte writable stores to Redux slices?▼

Complete the one-time setup first: install Themis, create an empty Store, and wire it into the root layout. Then migrate slice by slice, adding each reducer to the Store constructor map and starting its saga with store.runSaga from onMount.

Why does store.runSaga throw an error in my Svelte app?▼

runSaga throws when called before store.init() because the internal saga manager only starts during Store initialization. Always call store.init() first, then start app sagas from onMount or non-component code after init.

Can I import Themis utilities from the package root?▼

No, the package publishes no root runtime API or utils barrel. Import from public subpackages like @augmentcode/themis/svelte-store, @augmentcode/themis/saga, and @augmentcode/themis/types, or approved utility leaf subpaths.

Should I start the @internal_sagaManager saga manually?▼

No, the internal saga manager starts automatically during Store initialization under reserved @internal_ domains. App code should only start its own sagas with store.runSaga(sagaFn) and never register package-owned internals.