design-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use…
Apply the Law of Figure-Ground — establish which layer is foreground and actionable versus background. Use when designing modals, overlays, and depth. For emphasising one element among peers, use `von-restorff-effect`.
$ npx -y skills add Owl-Listener/designer-skills --skill law-of-figure-ground --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/law-of-figure-groundContext preview
The summary Claude sees to decide when to auto-load this skill.
Apply the Law of Figure-Ground — establish which layer is foreground and actionable versus background. Use when designing modals, overlays, and depth. For emphasising one element among peers, use `von-restorff-effect`.
name: law-of-figure-ground description: Apply the Law of Figure-Ground — establish which layer is foreground and actionable versus background. Use when designing modals, overlays, and depth. For emphasising one element among peers, use `von-restorff-effect`.
You are an expert in visual attention and the perceptual hierarchy of UI surfaces.
You apply the Law of Figure-Ground to ensure users can instantly identify what is foreground (the content or action) and what is background (the context or surface), and to control this relationship deliberately at every layer of the interface.
The mind automatically separates visual fields into a subject (the figure) and a context (the ground). Figure is perceived as being in front, bounded, and the focus of attention. Ground is perceived as behind, unbounded, and receding.
This parsing is not a choice — it is a perceptual reflex. Every UI surface triggers figure-ground separation. The question is whether you designed it deliberately or left it to chance.
| Figure (foreground) | Ground (background) | |---|---| | Appears in front | Appears behind | | Bounded — perceived as having edges | Unbounded — perceived as extending beyond the figure | | Focus of attention | Context for attention | | Higher contrast, richer texture or detail | Lower contrast, flatter, more uniform | | Typically smaller area | Typically larger area |
Elevation is the primary tool for figure-ground in layered design systems. A card elevated above a page surface is figure; the page is ground. The shadow signals depth, and depth signals foreground. Dropdowns, sheets, modals, and tooltips must appear above the surface they are called from — depth signals primacy.
A modal requires the background to recede. A scrim — a semi-transparent dark overlay — reduces the ground's visual presence so the modal can be unambiguous figure. Without a scrim, figure-ground is unclear and attention is split between the modal and the page beneath it.
High-contrast elements are perceived as figure; low-contrast elements as ground. Text on a surface works through figure-ground: the text is figure (high contrast, bounded by its line), the surface is ground (lower contrast, unbounded). When text and background share too similar a luminance value, figure-ground collapses and the text is no longer legible.
In navigation or lists, the selected item becomes figure; unselected items become ground. The selected state — a background fill, a bold type treatment, a color change — must make the figure-ground shift unambiguous. If the selected and unselected states are too similar, users cannot tell which item is active.
Ambiguous figure-ground occurs when the same element can be read as either figure or ground — the visual equivalent of the Rubin vase. In fine art and illustration this is sometimes intentional. In UI, it is almost always a failure.
If users cannot immediately parse what is content and what is surface, they cannot act with confidence.
Light and dark modes invert the typical luminance relationship between figure and ground. What was dark figure on a light ground becomes light figure on a dark ground. Shadows that read as elevation in light mode may become invisible in dark mode — use subtle light-colored borders or reduced-luminance fills to maintain figure-ground clarity when shadows disappear.
Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use…
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift…
Communicate design's contribution to business and user outcomes in stakeholder language. Use…
Build a QA checklist for verifying that a build matches the design. Use at implementation…
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships…
Plan and facilitate a design sprint from challenge framing through prototype testing. Use…