What problem does it solve? Buttons and controls can appear broken even when their handlers exist, never crash, and pass type checks, because a later call in the handler silently resets the state an earlier call set. This Skill finds those defects by tracing every interactive element through its full state-change sequence instead of reading code line by line. ## Core Features & Use Cases - Side-Effect Map: Builds a mandatory map of every store action (Zustand, Redux, context, signals) recording which fields each action sets and which it resets as an undeclared side effect. - Six Defect Patterns: Checks each trace against sequential undo, async races, stale closures, missing transitions, conditional dead paths, and effect interference. - Structured Reports: Produces severity-rated findings (CRITICAL to LOW) with numbered call sequences, expected versus actual state, and concrete fixes. - Use Case: After refactoring a shared Zustand store, a "New Email" button stops opening the compose form. The audit reveals that selectThread(null) resets composeMode as a side effect, undoing the setComposeMode(true) call that ran one line earlier. ## Quick Start Ask the assistant to run a click-path audit on the screen or store where a button does nothing despite its handler existing.
