law-of-similarity

Applies the Gestalt Law of Similarity to signal element relationships through shared visual attributes.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill law-of-similarity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: law-of-similarity
Source: https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/law-of-similarity
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill law-of-similarity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interfaces often fail to communicate which elements belong together, forcing users to guess at categories, interactive affordances, and status meanings. This Skill applies the Gestalt Law of Similarity so shared color, shape, size, and style consistently signal that elements belong to one category.

Core Features & Use Cases

  • Interactive state signaling: Gives all interactive elements a shared visual property so users can identify what is actionable without instruction.
  • Category and role coding: Establishes consistent color-to-meaning mappings for status indicators, destructive actions, and navigation sets.
  • Design system coherence: Keeps component attributes (corner radius, icon stroke, input height) uniform so unintended visual differences do not read as categorical differences.
  • Use Case: When auditing a dashboard, use this Skill to verify that all charts use the same color for the same data series and that no two buttons of the same type have diverging styles.

Quick Start

Review this screen using the law-of-similarity skill and flag any elements whose visual style breaks an established category grouping.

Frequently Asked Questions about law-of-similarity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use the Law of Similarity in UI design?

Give elements that share a category the same visual attributes such as color, shape, size, or style. Users will perceive them as related even when they are not spatially adjacent, so keep the coding consistent across the entire interface.

What is the difference between Law of Similarity and Law of Proximity?

Proximity groups elements by spatial closeness, while similarity groups them by shared visual attributes regardless of distance. When they conflict, similarity can override proximity, so a differently colored element reads as distinct even inside a tight group.

Why is color alone not enough for category coding?

Colorblind users cannot distinguish groups encoded only through hue, so color-only similarity fails for a significant portion of users. Always use redundant coding such as shape plus color so the grouping survives monochrome rendering and color vision deficiency.

How does similarity apply to design systems?

Similarity makes a design system feel coherent by keeping attributes like button shape, input height, and icon stroke weight uniform across components. Unintended differences, such as mismatched corner radii on the same button type, read as categorical differences and should be treated as bugs.

When should I use similarity instead of proximity for grouping?

Use similarity when related elements must be distributed across a layout, such as status indicators or data series in separate charts. Use proximity when elements are naturally co-located, and combine both for the strongest grouping signal.