memory-load-reduction

Name: memory-load-reduction
Author: Owl-Listener

82stars25forks

How to install memory-load-reduction?

owl-listener/inclusive-design-skills/memory-load-reduction

$npx -y skills add Owl-Listener/inclusive-design-skills --skill memory-load-reduction

Installs into the current project.

Summary

Design interfaces that minimise demands on working memory. Use when designing multi-step flows, dashboards, comparison tools, forms that span multiple screens, or any interface where users need to remember information across steps or sessions. Triggers on: memory, remember, forge

Files · 1

View on GitHub

SKILL.md

1	# Memory Load Reduction
2
3	Design systems that remember so users don't have to. Working memory holds
4	roughly 4 items. Every piece of information the user must carry across
5	screens, steps, or sessions is a potential failure point.
6
7	## Core Principle
8
9	If the system can remember it, the user shouldn't have to.
10
11	## Design Patterns
12
13	### Persistent Context
14	- Show key selections throughout a multi-step flow
15	(chosen product, plan, date visible on every step)
16	- Display running totals in shopping and financial contexts
17	- Keep the user's search query visible in results
18	- In multi-step forms, show a summary sidebar of completed steps
19
20	### Forward Carry
21	- Never re-ask information the system already has
22	- Pre-fill fields from earlier steps or previous sessions
23	- Carry context between screens (if the user selected "Business",
24	don't ask "Personal or Business?" again)
25	- Remember user preferences across sessions
26
27	### External Memory Aids
28	- "Compare" features so users don't need to remember options
29	- Recently viewed and recently used lists
30	- Copy-to-clipboard for reference numbers and codes
31	- Print-friendly versions of complex information
32	- Bookmarking or favouriting for later reference
33
34	### Save and Resume
35	- Auto-save progress in any flow longer than 3 steps
36	- Allow users to return to where they left off
37	- Show when progress was last saved
38	- Send a reminder link for abandoned multi-step tasks
39	- Never require starting over when a session expires
40
41	### Chunked Process
42	- Break tasks into 3–7 clearly labelled steps
43	- One decision per step where possible
44	- Allow forward and backward movement between steps
45	- Show progress: "Step 2 of 4: Choose your plan"
46	- Provide a review/summary screen before final submission
47
48	## Assessment Questions
49
50	1. Does the user need to remember anything from a previous screen?
51	2. Is any information hidden that the user might need to reference?
52	3. Can the user leave and come back without losing progress?
53	4. Are there places where the user needs to transfer information
54	between screens manually (e.g., write down a code)?
55	5. Does the system re-ask for information it already knows?

People who liked this also viewed

6 picks

Type

memory-load-reduction

82stars25forks

View on GitHub

How to install memory-load-reduction?

owl-listener/inclusive-design-skills/memory-load-reduction

$npx -y skills add Owl-Listener/inclusive-design-skills --skill memory-load-reduction

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Memory Load Reduction
2
3	Design systems that remember so users don't have to. Working memory holds
4	roughly 4 items. Every piece of information the user must carry across
5	screens, steps, or sessions is a potential failure point.
6
7	## Core Principle
8
9	If the system can remember it, the user shouldn't have to.
10
11	## Design Patterns
12
13	### Persistent Context
14	- Show key selections throughout a multi-step flow
15	(chosen product, plan, date visible on every step)
16	- Display running totals in shopping and financial contexts
17	- Keep the user's search query visible in results
18	- In multi-step forms, show a summary sidebar of completed steps
19
20	### Forward Carry
21	- Never re-ask information the system already has
22	- Pre-fill fields from earlier steps or previous sessions
23	- Carry context between screens (if the user selected "Business",
24	don't ask "Personal or Business?" again)
25	- Remember user preferences across sessions
26
27	### External Memory Aids
28	- "Compare" features so users don't need to remember options
29	- Recently viewed and recently used lists
30	- Copy-to-clipboard for reference numbers and codes
31	- Print-friendly versions of complex information
32	- Bookmarking or favouriting for later reference
33
34	### Save and Resume
35	- Auto-save progress in any flow longer than 3 steps
36	- Allow users to return to where they left off
37	- Show when progress was last saved
38	- Send a reminder link for abandoned multi-step tasks
39	- Never require starting over when a session expires
40
41	### Chunked Process
42	- Break tasks into 3–7 clearly labelled steps
43	- One decision per step where possible
44	- Allow forward and backward movement between steps
45	- Show progress: "Step 2 of 4: Choose your plan"
46	- Provide a review/summary screen before final submission
47
48	## Assessment Questions
49
50	1. Does the user need to remember anything from a previous screen?
51	2. Is any information hidden that the user might need to reference?
52	3. Can the user leave and come back without losing progress?
53	4. Are there places where the user needs to transfer information
54	between screens manually (e.g., write down a code)?
55	5. Does the system re-ask for information it already knows?

People who liked this also viewed

6 picks

Type