agentleFS
45ck45ck/hci-review-skill/.claude/skills/prototype-hci-pack/SKILL.md

prototype-hci-pack

Skill19 starsChanged 6 days agoMITView on GitHub

Create a full HCI review pack for a prototype: conceptual model, state model, journeys, glossary, information architecture, consistency audit, failure path audit, heuristic evaluation, cognitive walkthrough, scorecard, and summary.

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 16 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use ultrathink. Work from the current repository, current files, current screenshots, current docs, and current prototype state.

    line 11
  2. Distinctive:

    Ensure conceptual coherence across screens, flows, actions, and language.

    line 15
  3. Distinctive:

    Leave durable artifacts that can guide implementation.

    line 17
  4. Very specific:

    Write them to docs/hci/ unless the user asked for another path.

    line 24
  5. Distinctive:

    Create the directory if it does not exist.

    line 38
  6. Very specific:

    Use the conceptual-model skill logic:

    line 50
  7. Distinctive:

    create a compact state model in markdown or Mermaid if useful

    line 52
  8. Distinctive:

    create Mermaid state diagrams

    line 60
  9. Distinctive:

    check UI state coverage: does every state have a distinct visual treatment?

    line 61
  10. Distinctive:

    Create a glossary of canonical nouns, verbs, statuses, and labels.

    line 84
  11. Very specific:

    Create a hierarchical sitemap of all screens/pages/views

    line 94
  12. Distinctive:

    Document the navigation model: global, secondary, tertiary, escape hatches

    line 95
  13. Distinctive:

    Check action placement: is each action near the objects it acts on?

    line 97
  14. Distinctive:

    Create a table with:

    line 113
  15. Distinctive:

    Create a summary table: category, items audited, handled, partial, not handled, critical gaps.

    line 130
  16. Distinctive:

    After acting, will the feedback make sense?

    line 159
  17. Very specific:

    Create hci-scorecard.md rating the prototype 1-5 on each dimension:

    line 164
  18. Distinctive:

    Prefer recognition over recall.

    line 193
  19. Distinctive:

    Prefer stable conceptual models over screen-by-screen patching.

    line 194
  20. Distinctive:

    If the prototype is incomplete, still evaluate the structure that exists.

    line 196

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

Build a full solo-review pack for this prototype or interface area:

$ARGUMENTS

Use ultrathink. Work from the current repository, current files, current screenshots, current docs, and current prototype state. Do not wait for user research unless absolutely blocked. If something is unknown, make the smallest reasonable assumption and label it clearly.

Goals

  • Reduce confusion before user testing.
  • Ensure conceptual coherence across screens, flows, actions, and language.
  • Surface the highest-risk UX/HCI problems early.
  • Leave durable artifacts that can guide implementation.

Visual default for new high-fidelity prototypes

Use Apple-inspired Liquid Glass on navigation and controls when a new high-fidelity prototype has no established design system. Use solid surfaces for readable content and dense data. Keep the border highlight optional, preserve text contrast and keyboard focus, and provide an opaque fallback for reduced transparency. Respect the product’s design system, touch input and reduced motion. Evaluate the treatment against the task and the Quantitative HCI example.

Produce these outputs

Write them to docs/hci/ unless the user asked for another path.

  1. docs/hci/conceptual-model.md
  2. docs/hci/state-model.md
  3. docs/hci/user-journeys.md
  4. docs/hci/glossary.md
  5. docs/hci/information-architecture.md
  6. docs/hci/consistency-audit.md
  7. docs/hci/failure-path-audit.md
  8. docs/hci/heuristic-evaluation.md
  9. docs/hci/cognitive-walkthrough.md
  10. docs/hci/hci-scorecard.md
  11. docs/hci/hci-summary.md

Create the directory if it does not exist.

Required process

1) Understand the system

Extract and document:

  • primary user types or actors
  • primary objects/entities in the interface
  • major actions users can take
  • states for each important object
  • system rules, permissions, and transitions

Use the conceptual-model skill logic:

  • define users, objects, actions, states, rules
  • create a compact state model in markdown or Mermaid if useful
  • identify unclear or overloaded concepts

2) Define state models

For every stateful entity in the system:

  • list all states with meaning and user-visible cue
  • list allowed transitions with trigger, actor, and side effects
  • list invalid transitions with explanation
  • create Mermaid state diagrams
  • check UI state coverage: does every state have a distinct visual treatment?
  • flag ambiguous states, silent transitions, and undefined exits

3) Map the main journeys

Identify the 3 to 7 most important journeys for the scope. For each journey document:

  • user goal
  • entry point
  • steps
  • decision points
  • error paths
  • exit state
  • likely confusion points

Include Mermaid flowcharts where useful. Prioritize:

  • first-time user path
  • core happy path
  • edit/undo path
  • failure/recovery path
  • returning user path

4) Normalize language

Create a glossary of canonical nouns, verbs, statuses, and labels. For each term include:

  • canonical term
  • exact meaning
  • where it appears
  • terms to avoid or merge

Flag any concept drift such as one thing being called different names in different places.

5) Define information architecture

  • Create a hierarchical sitemap of all screens/pages/views
  • Document the navigation model: global, secondary, tertiary, escape hatches
  • Analyze grouping logic and label clarity
  • Check action placement: is each action near the objects it acts on?
  • Measure depth and breadth: flag paths that are too deep or orphaned screens

6) Audit consistency

Review consistency across screens and flows:

  • navigation placement
  • page titles
  • primary vs secondary actions
  • destructive actions
  • status presentation
  • empty/loading/error/success states
  • form layout and validation
  • icon meaning
  • modal, drawer, popover, and toast usage
  • back/cancel/close behavior

Create a table with:

  • item
  • expected invariant
  • observed variants
  • risk
  • recommendation

7) Audit failure paths

Review every non-happy-path state:

  • empty states: does each empty screen explain why and offer a next step?
  • loading states: is there always a loading indicator? timeout handling?
  • validation errors: inline or summary? specific or vague? data preserved?
  • permission failures: hidden, disabled, or error? explains how to fix?
  • network failures: retry available? data preserved?
  • partial completion: auto-saved? resumable?
  • undo/cancel/recovery: confirmation dialogs? soft delete?

Create a summary table: category, items audited, handled, partial, not handled, critical gaps.

8) Run heuristic evaluation

Apply Nielsen-style heuristics rigorously:

  • visibility of system status
  • match between system and real world
  • user control and freedom
  • consistency and standards
  • error prevention
  • recognition rather than recall
  • flexibility and efficiency of use
  • aesthetic and minimalist design
  • error recovery
  • help/documentation

Output a severity-ranked issues table:

  • ID
  • heuristic violated
  • where
  • evidence
  • why it matters
  • severity (0 to 4)
  • recommended fix

9) Run a cognitive walkthrough

For each critical journey, step through the interface and answer:

  1. Will the user form the right goal here?
  2. Will the user notice the correct action?
  3. Will the user understand that the action leads toward the goal?
  4. After acting, will the feedback make sense?

Log breakdowns with exact step references.

10) Score

Create hci-scorecard.md rating the prototype 1-5 on each dimension:

  1. Clarity of purpose
  2. Navigation clarity
  3. Terminology consistency
  4. State visibility
  5. Error prevention and recovery
  6. Recognition over recall
  7. Cross-screen consistency
  8. Failure path coverage

Include total score out of 40, top 3 strengths, top 3 weaknesses, and priority fixes.

For relevant interface patterns, use the Quantitative HCI catalogue at docs/hci/models/interface-design-models.md in the Quantitative HCI repository. Record the model ID, baseline, observed value, unit, sample size, test context, and evidence. If a measurement is missing, record how to collect it. Keep measurements alongside the scorecard's judgement scores.

11) Synthesize

Create hci-summary.md with:

  • one-paragraph context recap
  • top 5 confusion risks
  • top 5 design invariants to enforce
  • top 5 implementation priorities
  • open assumptions and unknowns

Quality bar

  • Be concrete, not generic.
  • Refer to actual files, screens, components, routes, or flows where possible.
  • Prefer recognition over recall.
  • Prefer stable conceptual models over screen-by-screen patching.
  • Distinguish structural issues from visual polish issues.
  • If the prototype is incomplete, still evaluate the structure that exists.

Deliverable style

  • Clear headings
  • Markdown tables
  • Mermaid diagrams where useful
  • Direct language
  • No filler

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.