What problem does it solve? Debugging Svelte/Redux application state at runtime is difficult when selectors stop updating, duplicate stores get initialized, or reducers silently break reference equality. This Skill documents the runtime inspection hooks exposed by Store.initDevTool() so you can diagnose these issues directly from the browser console. ## Core Features & Use Cases - Console State Inspection: Read the current state snapshot and dispatch actions manually through window.svelteRedux.reduxContext after devtools registration. - Multiple-Store Detection: Interpret the "Multiple Redux stores initialized" error and trace it back to duplicate store.init() calls or missing disposers in tests. - Reducer Reference-Equality Diagnostics: Enforce no-op reducer contracts in unit tests since no runtime reference-check middleware is wired. - Use Case: A selector stops re-rendering after an action fires. Open DevTools, inspect window.svelteRedux.reduxContext.state to confirm whether the slice changed, then check the action type namespace or selector memoization key accordingly. ## Quick Start Ask the AI to help inspect the current Redux store state from the browser console using window.svelteRedux.reduxContext and diagnose why a selector is not updating.
