core

Routes framework-independent Redux and redux-saga guidance for the Themis package.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working in the Themis package need consistent, framework-independent rules for Redux state, actions, reducers, sagas, and testing, but the guidance is spread across many leaf documents. This Skill acts as a router that directs you to the correct core leaf skill for each Redux or redux-saga task, preventing misuse of Redux Toolkit APIs and duplicated state ownership. ## Core Features & Use Cases - Core skill routing: Maps each task (state integrity, actions, reducers, sagas, channels, serialization, testing, debugging, verification) to the correct leaf SKILL.md file. - Custom Redux enforcement: Explicitly blocks Redux Toolkit APIs like createSlice and configureStore in favor of Themis custom utilities. - Preflight compliance workflow: Requires reading linked leaves, citing skills in handoffs, and producing verifier-ready evidence such as owner searches and focused tests. - Use Case: When adding a new Redux slice with a saga, use this Skill to load the state-integrity, file-structure, actions, reducers, sagas, and testing leaves so the implementation follows canonical ownership and naming rules. ## Quick Start Ask the AI to route your Themis Redux task, for example: load the core skill and the matching leaf skills before adding a new reducer and saga for workspace-scoped state.

Frequently Asked Questions about core

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

FAQPage Schema
How do I add a new Redux slice in the Themis package?▼

Create a slice directory with separate types, slice, selectors, and saga files, then register the reducer in the Store constructor and start the saga with store.runSaga. Use camelCase for the logical slice identity and action namespaces, and search for existing owners before adding actions or selectors.

Can I use Redux Toolkit createSlice with Themis?▼

No, Themis uses a custom Redux setup and explicitly forbids Redux Toolkit APIs such as createSlice, configureStore, and createAsyncThunk. Use the custom createAction and createReducer utilities from @augmentcode/themis instead.

What Redux state values are allowed in Themis reducers?▼

State must be structured-clone safe: primitives, arrays, plain objects, and Collection instances. Date, Map, Set, RegExp, Promise, Function, class instances, Error, and Symbol values are forbidden; store timestamps as numbers or ISO strings and errors as plain objects.

How do I debug Redux state in a Themis app?▼

After store.initDevTool() runs, inspect window.svelteRedux.reduxContext.state and dispatch actions from the browser console. For dispatch diagnostics, enable logReduxActions in the Store constructor options to see grouped action logs with path-keyed state diffs.

When should I use store pruning in Themis?▼

Store pruning is explicit-only: load the store-pruning leaf only when the user directly asks to remove unused Redux selectors, actions, reducers, sagas, exports, or orphaned helpers. It is never applied proactively during ordinary feature work.