Command
/heuristic
Produce a scored heuristic critique of the UI using Nielsen's 10 + 6 design laws + optional persona walkthroughs. Outputs a machine-parseable scorecard plus a 0-100 UsabilityScore (the judged companion to the deterministic UICraftScore).
One command from ui-craft.
shell
$ npx -y skills add educlopez/ui-craft --agent claude-codeShips with ui-craft. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/heuristic
Context preview
What this command does when you run it.
Produce a scored heuristic critique of the UI using Nielsen's 10 + 6 design laws + optional persona walkthroughs. Outputs a machine-parseable scorecard plus a 0-100 UsabilityScore (the judged companion to the deterministic UICraftScore).
Stats
Stars209
Forks9
LanguageGo
LicenseMIT
Ships with ui-craft
Command definition
heuristic.md
--- description: Produce a scored heuristic critique of the UI using Nielsen's 10 + 6 design laws + optional persona walkthroughs. Outputs a machine-parseable scorecard plus a 0-100 UsabilityScore (the judged companion to the deterministic UICraftScore). argument-hint: "[file or component path] [--persona=<name>]" --- Score the UI at `$ARGUMENTS` against Nielsen's 10 + 6 design laws. Load the `ui-craft` skill. **Step 1 — Load the methodology.** Read `references/heuristics.md` for the full rubric, scoring definitions, design law details, and the required output format. Do NOT invent a new format or a new scale. **Step 2 — Walk Nielsen's 10 heuristics.** Score each 1-5 per the rubric: - **1** blocks users · **2** severe friction · **3** works but confusing · **4** works, minor polish · **5** best-in-class For every heuristic, write a concrete finding — quote text, count elements, name the broken flow. Vague findings are rejected. **Step 3 — Audit the 6 design laws.** PASS / FAIL each with a specific detail: - Fitts's Law — touch target sizing, CTA placement - Hick's Law — choice density, nav + select sizing - Doherty Threshold — perceived latency, optimistic UI - Cleveland-McGill — chart encoding choice - Miller's Law — nav depth, form section counts - Tesler's Law — where complexity lives **Step 4 — Persona walkthrough (if `--persona=` present).** If the args include `--persona=<name>`, load `references/personas.md` and run the matching walkthrough checklist. Supported: `priya`, `jordan`, `adaeze`, `kwame`, `margo`, `all`. Output the walkthrough as a `| Checklist item | Pass/Fail | Finding | Impact |` table. Without the flag, skip this step.
