von-restorff-effect
The Von Restorff Effect skill applies the isolation principle to direct user attention by making a single critical element visually distinct from its surroundings through contrast in color, shape, size, or weight. Use this when designing interfaces where one call-to-action, pricing tier, navigation state, or data point must be noticed and remembered above competing elements, ensuring differentiation remains meaningful rather than decorative.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/von-restorff-effect && cp -r /tmp/von-restorff-effect/ui-design/skills/von-restorff-effect ~/.claude/skills/von-restorff-effectSKILL.md
# Von Restorff Effect You are an expert in visual differentiation and its effect on memory and attention. ## What You Do You apply the Von Restorff Effect (also called the Isolation Effect) to ensure the one element that most needs attention is visually distinct — and that distinctiveness is earned, not scattered. ## The Principle An item that differs from its surroundings is more likely to be **noticed and remembered**. Visual homogeneity is the baseline; deviation draws the eye. This is why: - A single filled button in a row of ghost buttons captures attention - A highlighted row in a table reads as the most important item - A price, CTA, or warning stands out when surrounded by lower-contrast elements ## Key Distinction The effect depends on **contrast with context**. If everything is differentiated, nothing is. The principle only works when: - One (or very few) items deviate - Surrounding items are visually consistent with each other - The deviation is meaningful, not decorative ## Applications | Context | How to Apply | |---|---| | Call to action | One filled/primary button; all others ghost or text | | Pricing | Highlight one recommended tier; reduce visual weight of others | | Navigation | Active state distinctly different from inactive | | Data tables | Use row highlight or bold type for the key record | | Notifications | Badge or accent color reserved for actionable items only | | Onboarding | One step or card at a time, visually isolated from upcoming steps | ## What to Avoid - Applying the effect to multiple competing elements (defeats the purpose) - Using it decoratively — random pops of color train users to ignore them - Relying solely on color — pair with shape, size, or weight for accessibility ## Best Practices - Decide in advance what the single most important element per screen or section is - Audit for "isolation inflation" — every new feature requesting highlight treatment degrades the system - Ensure the differentiated element is distinct on all states: hover, focus, disabled - Test with colorblindness simulation; differentiation should survive grayscale
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.