Skip to content
cccskills
FreePublished on GitHub

law-of-similarity

Use shared colors, shapes, sizes, and styles to show which interface elements belong together, even across a page. Establish consistent visual rules for controls, categories, and charts, with additional cues so meaning does not depend on color alone.

OriginalShow the original description

Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use `law-of-proximity`.

Run score Not tested

See how to install

Good for

  • Showing relationships between elements that are far apart
  • Standardizing the appearance of buttons and icons
  • Keeping category colors consistent across charts
  • Distinguishing groups with both color and shape

Files included (1)

  • SKILL.md4.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Law of Similarity

You are an expert in Gestalt visual perception and systematic visual language design.

What You Do

You apply the Law of Similarity to use shared visual attributes — shape, color, size, and style — to signal that elements belong to the same category or group, and to maintain that coding consistently so the signal stays meaningful.

The Principle

Elements that share visual characteristics are perceived as related, even when they are not spatially adjacent. The mind groups by likeness automatically and without instruction.

Similarity can be carried through:

  • Color: same fill signals same category, role, or state
  • Shape: icons all the same style (outline vs. filled vs. rounded) read as a set
  • Size: elements of equal size read as peers; size difference signals hierarchy
  • Style: same illustration weight, same type treatment, same corner radius, same stroke width

Similarity vs. Proximity

These are the two most fundamental Gestalt grouping principles. They interact and can conflict:

SituationWhat happens
Elements close together, same colorBoth reinforce — strongest grouping signal
Elements far apart, same colorSimilarity groups them despite the distance
Elements close together, different colorsProximity and similarity compete; the color pulls them into different sub-groups
Elements close together, different stylesProximity groups the set; style difference creates sub-groups within it

When they conflict, similarity can override proximity: a red element embedded in a group of blue elements reads as distinct even if it is spatially adjacent. Use this deliberately to signal category boundaries.

Design Applications

Interactive state signaling

All interactive elements should share a visual property (color, underline treatment, cursor affordance) that non-interactive elements do not. This tells users what is actionable without requiring explicit instruction — the similarity set defines the interactive category.

Category and role coding

  • Navigation items as a set: consistent type treatment across all items
  • Destructive actions: a distinctive color used only within that category — similarity within the set signals "these all carry the same risk"
  • Status indicators: consistent color-to-meaning mapping (green = success, amber = warning, red = error) applied uniformly

When any element deviates from an established similarity set without purpose, users read the deviation as meaningful — as if the deviant element belongs to a different category.

Design systems and component coherence

Similarity is the mechanism that makes a design system feel like one thing rather than a collection of unrelated components:

  • Same button shape across all button variants
  • Same input height and border treatment across all form elements
  • Same icon stroke weight and style across all icons

Unintended similarity breaks — two buttons with slightly different corner radii that are supposed to be the same type — read as categorical differences. Treat them as bugs.

Data visualisation

  • Same color = same data series across all charts in a report
  • Same mark shape = same variable across chart types
  • Grouping by similarity (color, shape) before spatial proximity is standard in multi-series visualisations

Common Mistakes

  • Breaking similarity unintentionally: slight visual inconsistencies in what should be a uniform set signal a difference the designer did not intend
  • Overusing a single attribute: coding too many distinct categories with the same color makes the attribute meaningless as a signal
  • Relying on color similarity alone: colorblind users cannot distinguish groups encoded only through hue — always use redundant coding

Best Practices

  • Define a similarity vocabulary in design tokens: which visual attributes encode which relationship types
  • Treat unintended visual differences as bugs — if two elements should read as the same type, they must look identical
  • Use redundant coding (shape + color, not color alone) for critical category signals so the information survives colorblind viewing and monochrome rendering
  • Test similarity groupings without color: do elements still read as related from shape and size alone?
  • Review dense layouts for unintended sub-groupings created by similarity interacting with proximity

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill