cognitive-walkthrough
Skill19 starsChanged 6 days agoMITView on GitHub
Step through a task as a first-time user and identify where intent, discoverability, feedback, or interpretation will break down.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- mastepanoski/claude-skillstheir own version, first seen Oct 13, 2026
- henrique-simoes/Istaratheir own version, first seen Sep 27, 2026
- kennyolofsson23-netizen/claude-code-configtheir own version, first seen Mar 16, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- alexj11324/Mikka★ 87same name
- mastepanoski/claude-skills★ 62same name
- henrique-simoes/Istara★ 15same name
- kennyolofsson23-netizen/claude-code-config★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository67 other files it gives its agents.
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- state-model-beadsSkill
- state-modelSkill
- task-analysis-writerSkill
- usability-test-plannerSkill
- vocabulary-audit-beadsSkill
- vocabulary-auditSkill
- wireframe-criticSkill
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Run a cognitive walkthrough for this task or flow:
- Distinctive: line 11
Use ultrathink. Act like a plausible first-time user with only the cues available in the interface.
- Very specific: line 14
Write docs/hci/cognitive-walkthrough.md unless the user asked for another path.
- Distinctive: line 15
Create the directory if it does not exist.
- Distinctive: line 21
After acting, will the feedback make sense?
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Run a cognitive walkthrough for this task or flow:
$ARGUMENTS
Use ultrathink. Act like a plausible first-time user with only the cues available in the interface. Use the actual prototype and codebase context.
Output
Write docs/hci/cognitive-walkthrough.md unless the user asked for another path.
Create the directory if it does not exist.
Required questions at every step
- Will the user form the right goal here?
- Will the user notice the correct action?
- Will the user understand that the action leads toward the goal?
- After acting, will the feedback make sense?
Required format
For each step include:
- step number
- user goal
- visible cues
- likely action
- walkthrough answers for Q1 to Q4
- breakdowns / confusion risks
- recommendation
Extra checks
Also flag:
- hidden prerequisites
- unclear affordances
- weak or missing feedback
- misleading labels
- dead ends
- unclear recovery path
Synthesis
End with:
- steps most likely to fail
- reasons first-time users may hesitate
- design changes most likely to improve task completion
Deliverable style
- Clear headings
- Markdown tables
- Mermaid diagrams where useful
- Direct language
- No filler
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
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.

