MCPInstall

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.

Installs
1.1K
Last 24h
+22
Trending rank
#5449
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/owl-listener/designer-skills --skill law-of-continuity
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads law-of-continuity automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

FAQ

What does the law-of-continuity skill do?

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.

How do I install law-of-continuity?

Run npx skills add https://github.com/owl-listener/designer-skills --skill law-of-continuity in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/law-of-continuity/ (personal) or .claude/skills/law-of-continuity/ (project).

Which AI agents can use law-of-continuity?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is law-of-continuity safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains law-of-continuity?

It is published by owl-listener in owl-listener/designer-skills. It has 1,096 recorded installs.

More from owl-listener/designer-skills

View all →

presentation-deck

owl-listener/designer-skills

Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.

Docs & Writing3.1K installs

typography-scale

owl-listener/designer-skills

Create a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use readable-measure; for judging type on an existing screen use critique-typography (visual-critique).

Frontend & Design2.6K installs

illustration-style

owl-listener/designer-skills

Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use icon-system (design-systems).

Media & Creative2.6K installs

visual-hierarchy

owl-listener/designer-skills

Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use critique-visual-hierarchy (visual-critique).

Frontend & Design2.5K installs

color-system

owl-listener/designer-skills

Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use dark-mode-design; for chart palettes use data-visualization; for multi-brand token architecture use theming-system (design-systems).

Frontend & Design2.5K installs

dark-mode-design

owl-listener/designer-skills

Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use color-system.

Frontend & Design2.5K installs

Popular frontend & design skills

View category →

setup-matt-pocock-skills

mattpocock/skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Frontend & Design1.1M installs

frontend-design

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

OfficialFrontend & Design1M installs

hyperframes-animation

heygen-com/hyperframes

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

prototype

mattpocock/skills

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Frontend & Design999.2K installs

hyperframes-core

heygen-com/hyperframes

The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

Frontend & Design930.5K installs

vercel-react-best-practices

vercel-labs/agent-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

OfficialFrontend & Design843.1K installs