agentleFS
Sign inStart free
kuker24kuker24/OpenCodeBestFriend/skills/click-path-audit/SKILL.md

click-path-audit

Skill0 starsChanged 2 months agoMITView on GitHub

Trace each user-facing control through its handler and shared-store writes to find sequential undo, async races, stale closures, and missing transitions. Use when buttons look wired but do nothing, or after a refactor of shared UI state. Not for exploratory browser QA (playwright-qa), ordinary red-green bugs (diagnosing-bugs), or visual layout (impeccable).

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not treat "handler exists and does not throw" as proof the button works.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Click-Path Audit

Find interaction bugs that unit-shaped checks miss: handlers whose later calls undo earlier writes, races, and labels that promise a state the store never reaches.

Boundaries & Handoffs

NeedRoute
Exploratory browser click-throughplaywright-qa
Unknown defect with a red reproductiondiagnosing-bugs
Visual hierarchy or layoutimpeccable
Chrome motion after the state is correctemil-design-eng
Handler vs shared-store sequential undo and final-state mismatchclick-path-audit

Procedure

Consult references/patterns.md for the six conflict patterns.

  1. Map stores first. For each action: fields set, fields reset as side effects. Flag actions that clear state they do not own.
  2. Audit each touchpoint in scope. Identify the handler. Trace every call in order. Record reads, writes, resets. Check whether a later call undoes an earlier write. Check whether the final state matches the control's label. Check async order.
  3. Report with file:line, pattern name, expected vs actual, and a specific fix.

Scope tightly. Full-app audits split by page only after the store map exists. Store-focused audits cover every consumer of a changed action.

Do not treat "handler exists and does not throw" as proof the button works.

Output

CLICK-PATH-NNN: [CRITICAL|HIGH|MEDIUM|LOW]
  Touchpoint / Pattern / Handler / Trace / Expected / Actual / Fix

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free