What problem does it solve? When a Redux dispatch behaves unexpectedly in a themis Store application, developers lack visibility into which action fired, whether state actually changed, and what the per-path differences were. This Skill explains how to enable the built-in Redux action logger and correctly interpret its console output. ## Core Features & Use Cases - Opt-in dispatch logging: Enable logReduxActions: true in the third constructor argument of Store, ReactStore, or StreamingStore to publish reduxAction stream events. - Console group interpretation: Read collapsed action groups, styled action/state records, and the path-keyed lazy changes diff to pinpoint what a dispatch modified. - Custom logger factories: Replace default console rendering with a typed loggerFactory that receives the six read-only trace streams. - Use Case: A saga-driven feature updates state incorrectly. Construct a diagnostic Store with logReduxActions: true, reproduce the issue, expand the action group, and inspect the changes diff to see the previous and next value at the offending state path. ## Quick Start Enable Redux action logging on a new Store instance and show me how to read the state diff for a specific dispatched action.
