consistency-audit
Skill19 starsChanged 6 days agoMITView on GitHub
Audit a prototype for cross-screen consistency in navigation, actions, states, patterns, and interaction rules.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Sunnyshinnny776/pm-agentic-cookbooktheir own version, first seen Oct 20, 2026
- igorkravcenko/snowshoetheir own version, first seen Oct 13, 2026
- lcandy2/agent-skillstheir own version, first seen Oct 5, 2026
- wanshuiyin/Anti-Autoresearchtheir own version, first seen Jun 27, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- wanshuiyin/Anti-Autoresearch★ 180same name
- lcandy2/agent-skills★ 4same name
- Sunnyshinnny776/pm-agentic-cookbook★ 4same name
- igorkravcenko/snowshoe★ 1same 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
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- 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, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use ultrathink. Review the interface as a system, not as isolated screens.
- Very specific: line 14
Write docs/hci/consistency-audit.md unless the user asked for another path.
- Distinctive: line 15
Create the directory if it does not exist.
- Very specific: line 25
search/filter/sort behavior
- Distinctive: line 45
Do not confuse deliberate variation with accidental inconsistency.
“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
Audit consistency for this scope:
$ARGUMENTS
Use ultrathink. Review the interface as a system, not as isolated screens.
Output
Write docs/hci/consistency-audit.md unless the user asked for another path.
Create the directory if it does not exist.
Check these invariants
- navigation location and behavior
- page title structure
- screen layout rhythm
- primary / secondary / destructive action treatment
- form field ordering and validation style
- status badge style and meaning
- empty/loading/error/success states
- search/filter/sort behavior
- modal / drawer / popover / toast usage
- back / cancel / close semantics
- icon meaning
- terminology
Required output tables
Invariants
| Area | Expected invariant | Observed variants | Risk | Recommendation |
Screen inventory
| Screen/route/component | Primary purpose | Main action | State coverage | Notes |
Required synthesis
Conclude with:
- top consistency breaks
- invariants that should be written into the design system
- issues likely to confuse users because similar things behave differently
Quality bar
Do not confuse deliberate variation with accidental inconsistency. Explain the difference.
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.

