Skip to content

@augmentcode/ag-redux-toolkit

Redux + Saga state management for Svelte apps — designed for AI agents. Includes runtime TypeScript source, AI skills, and reference documentation for robust, observable, high-performance state management.

core

core
94 linesSource

>-

Core Redux and saga routing

Use this skill for framework-independent Redux/redux-saga work in the ag-redux-toolkit package. It routes to the core skills that are not owned by the Svelte-specific or Streaming-specific taxonomy waves.

This package uses a CUSTOM Redux setup — not Redux Toolkit (RTK). Do not use createSlice, configureStore, createAsyncThunk, or any RTK API.

Preflight

  • Read this skill plus every linked core leaf that applies to touched files.
  • Cite the applicable skills and docs in implementation plans and handoffs.
  • Include verifier-ready evidence: owner searches, focused tests, validation scripts, or git diff --check depending on the change.
  • Stop and ask if a request crosses into Svelte-specific selector/component behavior or Streaming/Kefir-specific behavior.
  • Pair core with at most one concrete Store family for a given app/code path; core is shared Redux/redux-saga guidance and is not permission to integrate both Svelte and Streaming Store patterns in one app.

Core routing workflow

  1. Start with ./core-policy/SKILL.md for shared-state or architecture decisions.
  2. Add ./state-integrity/SKILL.md before adding/changing Redux state, actions, selectors, watchers, or saga registration.
  3. If and only if the user explicitly asks to prune unused Redux store surface area, add ./store-pruning/SKILL.md before deleting selectors, actions, reducers, sagas, exports, tests, or orphaned helpers.
  4. Add domain leaves that match the behavior being changed.
  5. Add ./testing/SKILL.md for reducer, saga, or verification changes.
  6. Add ./verifier/SKILL.md before handoff for reliability-sensitive reviews.

Core leaf routes

RouteUse when
./core-policy/SKILL.mdRedux ownership, side-effect boundaries, serializability, and utility reuse rules.
./state-integrity/SKILL.mdPreventing derived/duplicated Redux state and duplicate action/selector/saga ownership.
./store-pruning/SKILL.mdExplicit-only pruning of unused Redux selectors, actions, handlers, sagas, and orphaned store logic when the user asks for pruning.
./import-boundaries/SKILL.mdPublic package imports, saga import boundaries, and Store-first public subpackages.
./file-structure/SKILL.mdSlice file layout, type modules, sagas, and Store registration patterns.
./state-serialization/SKILL.mdStructured-clone-safe Redux state values.
./actions/SKILL.mdcreateAction and createAsyncAction action creators.
./reducers/SKILL.mdImmutable chained reducers and no-op reference equality behavior.
./sagas/SKILL.mdtyped-redux-saga flows, watchers, debounce, retry/timeout, and side-effect orchestration.
./saga-manager/SKILL.mdPackage-owned saga crash tracking, lifecycle, restart, and backoff mechanics.
./channel-effects/SKILL.mdGeneric EventChannel consumers for IPC, websocket, or DOM channels.
./selector-channels/SKILL.mdSaga reactions to selector value changes.
./wait-for/SKILL.mdOne-shot saga waits for selector predicates.
./local-storage/SKILL.mdSafe app-local localStorage persistence from sagas.
./collections/SKILL.mdNormalized Collection<T, K> entity state.
./domain-scoped-state/SKILL.mdState keyed by workspace, project, tenant, or domain id.
./boolean-preference/SKILL.mdBoolean set/toggle preference helper registration.
./testing/SKILL.mdReducer/saga testing, typed-redux-saga mocks, and reference equality assertions.
./debugging/SKILL.mdRuntime inspection and reducer reference-equality diagnostics.
./verifier/SKILL.mdReview quality gates for instruction drift, duplicate owners, and evidence.
./redux-saga/SKILL.mdGeneric upstream redux-saga API reference.
  • Svelte Store/component/selector lifecycle guidance lives under ../svelte/.
  • StreamingStore and Kefir/observable selector guidance lives under ../streaming/.
  • These concrete Store families are mutually exclusive per app. Mixed repositories may use different families in separate apps/packages/code paths, but one app must not combine both.
  • Migration lifecycle skills remain under ../svelte/migration/.