What problem does it solve? It prevents inconsistent Redux usage in the Themis codebase by defining binding rules for shared state, side effects, serialization, entity storage, and slice type boundaries before any code is edited. ## Core Features & Use Cases - Core Redux Rules: Eleven load-bearing rules covering canonical state, saga-owned side effects, serializable state, Collection-based entity storage, and single-owner actions/selectors/sagas. - Common Mistakes Catalog: Prioritized wrong-vs-correct code examples for derived state, family-local stores, $effect misuse, inline slice types, and leftover pass-through wrappers. - Compliance Contract: Requires agents to read linked skills, cite applicable rules in handoffs, and provide verifier-ready evidence such as searches, tests, or diff checks. - Use Case: When adding a new slice to the SvelteKit/Electron renderer, consult this policy to place types in {slice-name}-types.ts, store entities in Collection<T, K>, and move async workflows into sagas instead of component effects. ## Quick Start Ask the agent to review a planned Redux slice change against the core policy rules and cite which rules apply before writing any code.