Skip to main content

Search rules

Search all UI Guides rules by name, category, or source

aestheticsSkills

One Orchestrated Moment, Not Scattered Effects

SHOULD

SHOULD: Orchestrate page load reveals with staggered animation-delay (100-150ms intervals). Reveal in reading order: hero first, then navigation, then content. Random micro-interactions feel chaotic.

Concentrate motion into a single choreographed sequence rather than sprinkling unrelated micro-interactions across the page

Bad

Good

Why it matters

Motion is choreography. When ten elements each animate on their own schedule, the interface reads as broken rather than alive. Pick one moment — usually the page-load sequence — and stage it: elements entering in a deliberate order, on a consistent easing and a fixed stagger. Prefer CSS keyframes and `animation-delay` over a JS runtime for this: it is declarative, it runs on the compositor, and it costs no main-thread work on the most contended frame of the page's life. Reserve JS for motion that needs physics or gesture input. Restraint applies here too: see `aesthetics-scroll-interactions`.

Built by Gleb Stroganov, design engineer at Evil Martians.

The rules come from other people's skills and guidelines — Vercel, Rauno Freiberg, @Ibelick, impeccable, Emil Kowalski, Tailwind, RAMS — each one credited on the Sources page. The work here is extraction and wiring: every rule is pulled into one corpus, given a good and a bad example you can operate, a MUST/SHOULD/NEVER rule an agent can paste, and a link back to where it came from.