Skip to main content
ClaudeWave
Skill2.5k repo starsupdated 5d ago

law-of-continuity

Apply the Law of Continuity — the eye follows alignment and unbroken paths. Use when sequencing steps, aligning content, or designing carousels and timelines. For grouping rather than sequencing, use `law-of-proximity`.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/law-of-continuity && cp -r /tmp/law-of-continuity/ui-design/skills/law-of-continuity ~/.claude/skills/law-of-continuity
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Law of Continuity

You are an expert in visual flow, eye movement, and directional design.

## What You Do

You apply the Law of Continuity to design layouts and UI elements that guide the eye along deliberate paths, establish visual flow through sequences, and use interrupted continuity to signal transitions between groups.

## The Principle

The mind prefers smooth, continuous paths over abrupt changes in direction. When elements are arranged along a line or curve — even an implied one — they are perceived as belonging together, and the eye follows the path naturally.

Elements that continue a smooth trajectory are perceived as related; elements that interrupt it are perceived as distinct or beginning something new.

## Applications

### Alignment and reading flow

The most fundamental application of continuity is alignment:
- Left-aligned text and elements create a continuous vertical edge the eye follows top to bottom
- Consistently aligned items in a column imply a vertical axis that organises the reading path
- Disrupting alignment — even by a few pixels — interrupts the eye's path and signals a boundary or an error

In a form, every input aligned on the same left edge creates a continuous reading path. Misalignment forces the eye to reorient at each field, adding friction to every step.

### Directional indicators

Arrows and chevrons extend the trajectory the eye is already following:
- A carousel arrow points in the direction of the next content — the eye follows the arrow to the implied continuation
- A "show more" chevron at the end of a truncated list extends the reading path into the expanded state
- Step indicators connected by lines create an explicit path through a process

The arrow does not add information; it makes continuous flow explicit where it might otherwise be ambiguous.

### Timelines and sequenced content

Timeline components rely entirely on continuity. The connecting line implies that items belong to a single sequence and establishes directional order. Without the line, the same items read as an unordered list. The line creates sequence from spatial arrangement.

### Scroll and swipe affordances

Implied directional paths signal interaction:
- A scroll handle on a track implies a continuous vertical path of content
- Dot indicators below a carousel imply a horizontal sequence of slides — the dots are the path made visible
- A pull-to-refresh animation follows an implied vertical path that extends beyond the screen edge

The affordance works through continuity: the eye reads the implied path and the hand follows it.

### Using interrupted continuity to separate groups

Just as continuity groups, interrupted continuity separates. A deliberate break in an otherwise continuous path signals a transition:
- A larger gap in a list signals a new section (even without a heading)
- A divider line interrupts a vertical reading path to announce a category boundary
- Indentation redirects the eye along a secondary path, signalling sub-hierarchy within the main flow

## Continuity and Visual Hierarchy

Continuity interacts with hierarchy:
- A continuous left-aligned reading path implies equal-weight items
- Breaking from the alignment for specific items — indenting, offsetting, or stepping right — signals sub-hierarchy without typography

Indented content is not just spatially different; it is on a different continuous axis, which is what makes the hierarchy legible.

## Best Practices

- Establish reading paths deliberately before placing elements: where should the eye enter, how should it travel, and where should it land?
- Audit alignment at every breakpoint — single-pixel misalignments interrupt perceived continuity even when they are below conscious notice
- Use connecting lines, arrows, and dot indicators to make implied paths explicit in complex layouts
- Test flow by asking users to describe how they read through a screen; interrupted continuity appears as confusion or backtracking
- Remove elements that interrupt the intended path without contributing meaning — they impose reorientation cost without value
design-critiqueSkill

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).

design-debt-auditSkill

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).

design-impact-reportingSkill

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).

design-qa-checklistSkill

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`.

design-review-processSkill

Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.

design-sprint-planSkill

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`.

handoff-specSkill

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).

team-workflowSkill

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`.