click-path-audit
Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.
- installs 8w
- 1,525
- 30-day movement
- starts with the next reading
- Related entries
- 5
- Connections
- 0
A skill that audits every user-facing button or touchpoint through its full state-change sequence to find interaction bugs that static code reading misses, such as handlers that undo each other, async races, and stale closures. It works in three steps: map state store side effects, audit each touchpoint against six named bug patterns, then report findings.
Reach for it when systematic debugging finds no bugs but users still report broken buttons, or after refactors touching shared state stores.
Use it to
- Audit UI touchpoints after a shared-state store refactor
- Trace sequential handler interactions for undo-style bugs
- Check for async races and stale closures in button flows
- Scope a full-app behavioural audit across parallel agents
- Verify UI state consistency before completion checks
For Developers debugging UI state bugs in agent-assisted codebases
- Host repository
- affaan-m/ECC
- Installs, lifetime
- 2,900
- Installs, 8 weeks
- 1,525
- Host stars
- 261k
- Host language
- JavaScript