About cognitive-load-assessment
cognitive-load-assessment is a design skill for evaluating interface cognitive load, intended for designers reviewing user flows screen by screen. It distinguishes task complexity, design-added burden, and goal-directed effort, then prioritizes recommendations by impact.
Key features
- 01Assess three types of cognitive load
- 02Review decisions, memory, and steps per screen
- 03Identify points where load spikes
- 04Apply strategies to reduce extraneous load
- 05Prioritize recommendations by impact
Use cases
- 01Assess complexity in signup or checkout flows
- 02Find issues with navigation, labels, and visual layout
- 03Plan redesigns for high-load screens
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/cognitive-load-assessmentin Claude Code to confirm it loaded.
Details
From the project READMECognitive Load Assessment
Assess cognitive load across three dimensions and provide actionable recommendations to reduce unnecessary burden on users.
The Three Types of Cognitive Load
Intrinsic load — complexity inherent in the task itself. A tax return is intrinsically complex. You cannot simplify the tax code. Focus: break into manageable steps, provide context, explain terms.
Extraneous load — complexity added by the design, not the task. Confusing navigation, unclear labels, inconsistent patterns, visual clutter. Focus: eliminate ruthlessly. Every instance is a fixable design failure.
Germane load — effort invested in the actual task. This is the load you WANT. The user engaging with their real goal. Focus: maximise this by removing the other two.
Assessment Framework
For each screen or step, evaluate:
| Dimension | Low (good) | Medium (review) | High (redesign) |
|---|---|---|---|
| Decisions required | 0–1 | 2–3 | 4+ |
| Items to remember | None | 1–2 | 3+ |
| New concepts to learn | None | 1 | 2+ |
| Steps to complete | 1–2 | 3–5 | 6+ |
| Reading complexity | Plain language | Some jargon | Dense/technical |
| Visual complexity | Clean, focused | Moderate | Cluttered |
If any dimension rates High, that screen needs redesign before launch.
How to Assess
- Walk through the flow as a user who is tired, stressed, and unfamiliar
- At each screen, count: decisions, things to remember, new concepts
- Note where you pause, re-read, or feel uncertain — those are load spikes
- Map the load type: is the difficulty intrinsic or extraneous?
- Recommend specific reductions for each extraneous load source
Reduction Strategies
- Progressive disclosure: show only what the current step needs
- Smart defaults: pre-select the most common option
- Chunking: group into sets of 3–5 related items
- Recognition over recall: show options, don't make users remember
- Persistent context: show key selections throughout a flow
- One primary action per screen: de-emphasise secondary actions
Output Format
Present the assessment as a screen-by-screen table showing load ratings, followed by prioritised recommendations sorted by impact.