svelte

Route Svelte and SvelteKit state management tasks to Themis Redux and saga guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Svelte and SvelteKit apps using the Themis state library need consistent rules for wiring the Store class, creating selector readables, dispatching actions, and migrating legacy Svelte stores to Redux slices without lifecycle crashes or duplicated state ownership. ## Core Features & Use Cases - Routing Index: Directs frontend tasks with concrete Svelte/SvelteKit evidence to the correct leaf skills for selectors, component integration, Store lifecycle, and migration. - Selector Lifecycle Guardrails: Defines the three selector call modes (component-init readable, .select(state) one-shot reads, .effect() in sagas) to prevent lifecycle_outside_component crashes. - Migration Playbook: Provides an ordered workflow to convert writable/derived stores and $state/$derived runes into Redux slices, selectors, and sagas with cleanup verification. - Use Case: When adding a shared todo list across SvelteKit routes, the skill routes you to core policy, state-integrity, actions, reducers, and selectors guidance so the slice has canonical owners and passes architecture validation. ## Quick Start Ask the agent to wire a Themis Store into a SvelteKit root layout and migrate an existing writable store into a Redux slice with selectors and a saga.

Frequently Asked Questions about svelte

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

FAQPage Schema
How do I wire a Redux store into a SvelteKit root layout?▼

Create a single Store instance from @augmentcode/themis/svelte-store at module scope with your reducers, then call store.init() in +layout.svelte during component initialization and register the returned disposer with onDestroy. Start app sagas explicitly with store.runSaga(sagaFn) from onMount.

How do I migrate Svelte writable stores to Redux?▼

Convert each writable() or $state field into slice initial state plus createAction and createReducer with immutable updates. Migrate one store at a time, move side effects into sagas, swap component imports to selector readables, then delete the old .store.svelte.ts file after verifying zero references.

Why does calling a selector throw lifecycle_outside_component?▼

The readable call form selectFoo() uses Svelte getContext(), which is only valid during component initialization. In event handlers, callbacks, async code, or tests, use selectFoo.select(store.state, args) for one-shot reads or yield* selectFoo.effect(args) inside sagas.

Can I use Redux Toolkit with this Svelte state setup?▼

No. This package uses a custom Redux setup, so createSlice, configureStore, and createAsyncThunk are not allowed. Use the package's createAction, createReducer, and store.createSelector APIs, and run the architecture validation gate to confirm compliance.

When should component state stay local instead of moving to Redux?▼

Keep ephemeral UI state local, such as hover, focus, open/closed toggles, scroll position, and single-form field values used by one component. Move state to Redux when it is shared across components, persisted, async-driven, or synced with storage, server, or IPC.