heuristic-eval-beads
Skill19 starsChanged 6 days agoMITView on GitHub
Run a heuristic evaluation and create Beads issues from the findings. Converts Nielsen heuristic violations into trackable Beads tasks with priorities and dependencies.
- Installs packages
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
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- 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
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Run a Heuristic Evaluation on the current prototype, then create Beads issues from the findings so they become trackable tasks.
- Distinctive: line 14
Run a heuristic evaluation for this scope:
- Distinctive: line 18
Use ultrathink. Use the actual prototype, repo, screenshots, routes, components, and docs.
- Very specific: line 21
Write docs/hci/heuristic-evaluation.md unless the user asked for another path.
- Distinctive: line 22
Create the directory if it does not exist.
- Very specific: line 67
Check if the bd CLI is available:
- Very specific: line 73
If
bdis not found: Stop here. Output the Heuristic Evaluation only, and append: - Distinctive: line 90
Check if the repo is already initialized:
- Very specific: line 96
If that fails (no .beads/ directory, not initialized):
- Very specific: line 102
Use --stealth so Beads metadata is not committed to the main repo.
- Distinctive: line 106
Create one parent issue to group all findings from this evaluation:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run a Heuristic Evaluation on the current prototype, then create Beads issues from the findings so they become trackable tasks.
This is an add-on to heuristic-eval. Run the full evaluation first, produce the complete artifact, then pipe findings into Beads.
Phase 1: Run the Heuristic Evaluation
Run a heuristic evaluation for this scope:
$ARGUMENTS
Use ultrathink. Use the actual prototype, repo, screenshots, routes, components, and docs. Do not give generic advice. Anchor every issue to a real part of the system where possible.
Output
Write docs/hci/heuristic-evaluation.md unless the user asked for another path.
Create the directory if it does not exist.
Heuristics to apply
- Visibility of system status
- Match between system and the real world
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors
- Help and documentation
Required output table
| ID | Heuristic | Screen/flow/component | Evidence | Why it matters | Severity (0-4) | Recommendation |
Severity rubric
- 0 = not a problem
- 1 = cosmetic / low priority
- 2 = minor usability issue
- 3 = major usability issue
- 4 = severe / likely to block or mislead users
Required synthesis
End with:
- top 5 highest-severity problems
- quickest wins
- structural issues that need redesign rather than visual tweaks
Note: if a consistency-audit artifact exists for this scope, reference it for heuristic #4 rather than re-auditing consistency in full. Apply heuristic #4 only to findings not already covered.
Deliverable style
- Clear headings
- Markdown tables
- Mermaid diagrams where useful
- Direct language
- No filler
Phase 2: Beads Integration
Step 1 -- Detect Beads
Check if the bd CLI is available:
command -v bdIf bd is not found: Stop here. Output the Heuristic Evaluation only, and append:
## Beads Integration: Skipped
`bd` CLI not found. To install Beads and create trackable issues from this review:
pip install beads-cli
# or see https://github.com/steveyegge/beads
Then re-run: /heuristic-eval-beadsIf bd is found: Continue to Step 2.
Step 2 -- Initialize Beads (if needed)
Check if the repo is already initialized:
bd ready --jsonIf that fails (no .beads/ directory, not initialized):
bd init --stealthUse --stealth so Beads metadata is not committed to the main repo.
Step 3 -- Create parent issue
Create one parent issue to group all findings from this evaluation:
bd create "Heuristic Evaluation: <branch> — <scope>" -p 1 --jsonCapture the parent issue ID from the JSON output. Store scope and summary:
bd update <parent-id> --description "<1-2 sentence scope summary>" --acceptance "<quality bar from the review>" --notes "Review date: <today>. Scope: <arguments>."Step 4 -- Create child issues per finding
For each Nielsen heuristic violation found with severity 0-4:
MAJOR findings -- always create:
Severity 3-4 heuristic violations:
bd create "[MAJOR] <finding-title>" -p 0 --jsonMINOR findings -- create only if the user passed --include-minor. Otherwise skip and note them in the output.
Severity 1-2 heuristic violations:
bd create "[MINOR] <finding-title>" -p 2 --jsonFor each created issue, update with structured fields (do NOT use bd edit):
bd update <child-id> --description "<what/why + evidence>" --notes "<location and context>" --acceptance "<fix recommendation or verification>"Then link child to parent:
bd dep add <child-id> <parent-id>Step 5 -- Show next actions
bd ready --jsonOutput
Return a combined report with two sections:
Section A: Heuristic Evaluation
- Issues table (ID, heuristic, location, evidence, severity, recommendation)
- Top 5 highest-severity problems
- Quickest wins
- Structural issues needing redesign
Section B: Beads Integration Summary
- Status: initialized | already-initialized | skipped (with reason)
- Parent bead:
<id>--<title> - Created beads: table of Bead ID | Severity | Finding Title | Priority
- Skipped findings: list with reasons (e.g., "MINOR, --include-minor not set")
- Next actions: output of
bd ready --json
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.

