agentleFS
sukirman1901sukirman1901/frontend-expert/skills/motion/SKILL.md

motion

Skill9 starsChanged 2 months agoMITView on GitHub

Purposeful UI motion by family/pattern — shell defaults (fade, drawer, press) plus marketing vocabulary (reveal, scroll, text, carousel, hero, …). Hand-roll CSS/Motion/GSAP from named patterns. Use for animation requests, landings, marquees, parallax, text reveal, and light defaults on /ui shells — not token-only tweaks.

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 9 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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not stack Hero + 3D + Text + Spotlight + Carousel in one viewport

    line 79

“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

Overview

Motion clarifies hierarchy and feedback — it does not decorate. Pick families/patterns by name, then hand-roll (CSS / Motion / GSAP). Do not default to third-party registry installs.

Full catalog: references/motion-families.md (12 families · 144 patterns).

When to Use

  • Micro-interactions (hover, focus, press)
  • Enter/exit or layout transitions (section swaps, drawers, modals)
  • Scroll-linked, text, carousel, hero, or other named patterns
  • Default (light): app shell / dashboard / multi-section /ui — section fade + drawer slide + smooth scroll (unless user forbids)

When to skip

  • Static token/color-only tweaks
  • User asked for zero animation / “tanpa animasi”
  • Inspecting / explaining existing motion → motion-inspection

Reduced-motion users still need state changes and usable instant/opacity fallbacks; skip spatial/decorative effects, not the interaction contract.

Lanes

LanePeruntukanDefaults
Product / shellApp chrome, settings, dashboardsfade-up / page-crossfade, drawer-slide, press-scale, lift-hover
Marketing / expressiveLanding, campaignsChoose 1–2 families + 1–2 patterns from catalog — budget 2–3 motions / viewport

Family peruntukan (quick)

FamilyUntukBukan untuk
Micro InteractionToggle, toast, like, progressHero / scroll story
Hover & InteractionLift, press, magnetic, tiltPage enter
Scroll-basedSticky, horizontal, scroll-zoomButton-only micro
Reveal & WipeEnter fades, split, mask, drawerEndless loops as only motion
Text MotionWord reveal, typewriter, marquee typeForms / dense settings
Carousel & Continuous FlowMarquee, filmstrip, snapSingle CTA focus pages
Grid MotionBento, flip grid, reflowOne-button chrome
Spotlight & FocusCenter stage, dim siblingsWhole-page noise
Stack & ScatterDeck, fan, swipe deckAdmin tables
Hero Section MotionParallax / float device / auroraApp shell (max 1 signature)
Morph & TransformShared element, FAB morphEvery navigation
3D & PerspectiveOrbit, coverflowDefault product UI

Workflow

  1. Lane — product shell vs marketing
  2. Family — match peruntukan (max 2 families)
  3. Patterns — name 1–2 from motion-families.md; read definisi + hand-roll hint
  4. Contract + implement — record trigger/state identity, properties, interruption, input alternatives and reduced-motion endpoint (motion.md). Prefer transform/opacity; use bounded measured size/layout when disclosure or morph requires it.
  5. Budget — ≤2–3 intentional motions per viewport
  6. A11y — prefers-reduced-motion: reduce (opacity/instant fallbacks); never meaning-by-motion-alone
  7. Report — Conventions: Motion: light shell | families: Hover+Reveal | patterns: lift-hover, fade-up; distinguish source/state checks from actual target playback and performance measurements.

Shell defaults (product)

  • Section enter: fade-up ~250–300ms
  • Mobile drawer: drawer-slide + backdrop fade
  • Controls: press-scale (0.96)
  • scroll-behavior: smooth (disabled under reduced-motion)

Smooth scroll is not permission to auto-scroll incoming data. Product-state recipes in references/motion.md govern chart updates, disclosure and stream-follow; a reader who scrolls upward keeps control.

Hard rules

  • Hand-roll from pattern names — registry install is not the pack default
  • Do not stack Hero + 3D + Text + Spotlight + Carousel in one viewport
  • Marketing: max one Hero signature pattern

Checklist

  • Lane chosen (product vs marketing)
  • Family peruntukan matches the ask (≤2 families)
  • Named patterns listed (≤2–3 motions in viewport)
  • Hand-rolled from definisi (not registry-as-answer)
  • prefers-reduced-motion handled
  • Rapid reversal, nested motion, focus/keyboard and gesture cancellation checked where relevant; final data/state stays truthful
  • No layout-thrashing / decorative spam
  • Conventions Motion line filled

Depth

  • Vocabulary: references/motion-families.md
  • Recipes: references/motion.md
  • Micro craft overlap: polish
  • Demo shell: local test/ sandbox (optional; not shipped)

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.