mcpField
M
memory-load-reduction

memory-load-reduction

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

About memory-load-reduction

A cognitive-load design skill for interface designers, focused on reducing what users must remember across screens and sessions. It covers persistent context, carried-forward information, saved progress, and chunked flows.

Key features

  1. 01Keep key selections and context visible
  2. 02Carry known information into later steps
  3. 03Offer comparison and recent-use aids
  4. 04Save progress and resume tasks
  5. 05Break flows into labelled steps with progress

Use cases

  1. 01Design multi-step forms and checkout flows
  2. 02Avoid asking again for information already collected
  3. 03Let users resume unfinished tasks

Install

Copy the command and run it in a terminal.

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

After installing, type/memory-load-reductionin Claude Code to confirm it loaded.

Details

From the project README

Memory Load Reduction

Design systems that remember so users don't have to. Working memory holds roughly 4 items. Every piece of information the user must carry across screens, steps, or sessions is a potential failure point.

Core Principle

If the system can remember it, the user shouldn't have to.

Design Patterns

Persistent Context
  • Show key selections throughout a multi-step flow (chosen product, plan, date visible on every step)
  • Display running totals in shopping and financial contexts
  • Keep the user's search query visible in results
  • In multi-step forms, show a summary sidebar of completed steps
Forward Carry
  • Never re-ask information the system already has
  • Pre-fill fields from earlier steps or previous sessions
  • Carry context between screens (if the user selected "Business", don't ask "Personal or Business?" again)
  • Remember user preferences across sessions
External Memory Aids
  • "Compare" features so users don't need to remember options
  • Recently viewed and recently used lists
  • Copy-to-clipboard for reference numbers and codes
  • Print-friendly versions of complex information
  • Bookmarking or favouriting for later reference
Save and Resume
  • Auto-save progress in any flow longer than 3 steps
  • Allow users to return to where they left off
  • Show when progress was last saved
  • Send a reminder link for abandoned multi-step tasks
  • Never require starting over when a session expires
Chunked Process
  • Break tasks into 3–7 clearly labelled steps
  • One decision per step where possible
  • Allow forward and backward movement between steps
  • Show progress: "Step 2 of 4: Choose your plan"
  • Provide a review/summary screen before final submission

Assessment Questions

  1. Does the user need to remember anything from a previous screen?
  2. Is any information hidden that the user might need to reference?
  3. Can the user leave and come back without losing progress?
  4. Are there places where the user needs to transfer information between screens manually (e.g., write down a code)?
  5. Does the system re-ask for information it already knows?

Comments

Markdown supported