What problem does it solve? Svelte components that subscribe to Redux-style selectors can re-render excessively when every state write triggers an emission. This Skill enforces Store-owned selector scheduling so emissions are coalesced and throttled correctly, and prevents developers from adding duplicate debounce, timer, or caching layers that cause stale updates. ## Core Features & Use Cases - Store-first selector creation: Define selectors through store.createSelector(...) and tune coalescing only via the throttledSelectorFrequency Store option (default 64 FPS, range 1-256). - Correct read patterns: Call selector readables at component init, use .select(store.state, ...) for one-shot handler reads, .effect() in sagas, and .withStore(store) for explicit binding. - Anti-pattern guardrails: Blocks wrapping selector readables in memoize, debounce, rAF, or writable-proxy layers, and forbids using readables as audit/event streams. - Use Case: A pointer-tracking component re-renders on every mousemove write. Use this Skill to rely on the Store's built-in rAF coalescing instead of hand-rolling a debounced writable, and move audit logging into an action-driven saga. ## Quick Start Ask the assistant to review your Svelte selector usage and configure Store-owned selector scheduling with the correct throttledSelectorFrequency instead of manual debounce wrappers.
