mcpField
A
assess-load

assess-load

github.com/owl-listenerDesign & UI10875 installsUpdated 20w ago
Repository

About assess-load

assess-load is a design skill for mapping cognitive load across a multi-step process and locating points where users may struggle or make errors. It guides teams from journey mapping and load ratings to navigation checks and targeted design recommendations.

Key features

  1. 01Maps each step in a user journey
  2. 02Rates six cognitive-load dimensions
  3. 03Identifies load spikes and memory bridges
  4. 04Checks navigation, saved progress, and carried context
  5. 05Recommends changes and an overall load score

Use cases

  1. 01Reviewing a multi-step form for difficult steps
  2. 02Finding where users must recall earlier information
  3. 03Prioritizing changes to reduce sustained cognitive load

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/inclusive-design-skills --skill assess-load

After installing, type/assess-loadin Claude Code to confirm it loaded.

Details

From the project README

Assess Load

Map the cognitive load across a complete multi-step process and identify where users are most likely to struggle, give up, or make errors.

Process

Step 1: Map the Journey

List every step in the process from start to completion. For each step, note: what the user sees, what they must do, and what they must decide.

Step 2: Rate Each Step

Using cognitive-load-assessment, evaluate each step across all six dimensions (decisions, memory, concepts, steps, reading, visual). Record the rating for each.

Step 3: Identify Load Spikes

Plot the load across the journey. Identify:

  • Steps where load suddenly increases (load spikes)
  • Consecutive steps with medium-or-higher load (sustained load)
  • Points where users must remember information from earlier steps (memory bridges)
Step 4: Check Navigation and Memory

Using wayfinding-navigation and memory-load-reduction, verify:

  • Can users always get back to a previous step?
  • Is progress saved automatically?
  • Is key context carried forward between steps?
  • Can users see where they are in the overall process?
Step 5: Recommendations

For each load spike or sustained load zone, recommend specific design changes to bring the load rating down.

Output

Deliver a cognitive load map: a step-by-step table showing the load rating at each point in the journey, annotated with:

  • Load spikes flagged in red
  • Memory bridges highlighted
  • Specific reduction recommendations for each issue
  • An overall cognitive load score for the process

Comments

Markdown supported