agentleFS
F0rger123F0rger123/CLAUDE-DESIGN-GOD-MODE/skills/motion/SKILL.md

motion

Skill1 starsChanged 19 days agoMITView on GitHub

Use when adding, reviewing or fixing animation and transitions in a web UI - hover and press feedback, modals, dropdowns, toasts, page and scroll reveals, springs, easing and durations. Decides whether something should animate at all, then how, with reduced-motion support.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use defaults, viewports and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sanmidableSkill

    defaults

    Also in 3 projects that use this

  • sanmidableSkill

    viewports

    Also in 3 projects that use this

  • miovragSkill

    keyboard

    Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.

    Also in 3 projects that use this

  • soilmassSkill

    color

    Color animations including hue shifts, saturation changes, brightness transitions, and contrast adjustments. Use when implementing color morphing, theme transitions, mood effects, or attention-grabbing color pulses. Provides tokens for all color property animations.

    Also in 4 projects that use this

  • owshq-mecSkill

    layout

    Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

    Also in 3 projects that use this

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never animate keyboard-triggered actions.

    line 19
  2. Very specific:

    Never ease-in for UI; it feels laggy at the moment the user is watching.

    line 26
  3. Very specific:

    Prefer CSS transitions and @starting-style for simple enter/exit.

    line 40
  4. Distinctive:

    Keep opacity changes and state colour.

    line 53
  5. Very specific:

    When reviewing motion code, answer with a table: | Before | After | Why |, one row per issue.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Motion

Motion explains change and confirms input. If it does neither, it is decoration and needs a reason.

1. Should it animate?

How often the user sees itDecision
100+ times a day (shortcuts, palette toggle, typing)Never animate
Tens of times (hover, list navigation, tabs)Tiny or none (colour/opacity under 150ms)
Occasionally (modal, drawer, toast, dropdown)Standard transition
Rarely (onboarding, success, first visit hero)Room for delight

Never animate keyboard-triggered actions.

2. Easing

  • Entering or exiting: strong ease-out cubic-bezier(.23, 1, .32, 1).
  • Moving on screen: ease-in-out cubic-bezier(.77, 0, .175, 1).
  • Drawers/sheets: cubic-bezier(.32, .72, 0, 1).
  • Colour/hover: ease. Constant motion (marquee, progress): linear.
  • Never ease-in for UI; it feels laggy at the moment the user is watching.

3. Duration

Press 100-160ms · tooltip 125-200ms · dropdown 150-250ms · modal/drawer 200-400ms · marketing hero up to 800ms. Exits ~20% faster than entrances. UI motion stays under 300ms.

4. Craft rules

  • Animate transform and opacity only. Never width, height, top, left, or transition: all.
  • Nothing appears from scale(0); start at scale(.95) + opacity: 0.
  • Popovers and menus scale from their trigger (transform-origin at the trigger). Modals stay centred.
  • Buttons: :active { transform: scale(.97) } with a 120ms transition.
  • Tooltips: delay the first one (~400ms); adjacent ones open instantly.
  • Stagger lists by 30-50ms per item, cap the total under 400ms.
  • Scroll reveals: one per page at most, small distance (8-16px), run once. Not on every section.
  • Springs (Motion/Framer, React Spring) for drag, gestures and interruptible movement: { type: "spring", duration: .4, bounce: .15 }. Keep bounce at 0.1-0.3, and only on playful surfaces.
  • Prefer CSS transitions and @starting-style for simple enter/exit; the View Transitions API for page/state morphs; a JS library only when gestures or sequences need it.

5. Reduced motion (required)

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: .01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: .01ms !important;
    scroll-behavior: auto !important;
  }
}

Keep opacity changes and state colour; remove movement, parallax and shake.

Review format

When reviewing motion code, answer with a table: | Before | After | Why |, one row per issue.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.