sukirman1901/motion

O que motion faz?

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

Lane	Peruntukan	Defaults
Product / shell	App chrome, settings, dashboards	fade-up / page-crossfade, drawer-slide, press-scale, lift-hover
Marketing / expressive	Landing, campaigns	Choose 1–2 families + 1–2 patterns from catalog — budget 2–3 motions / viewport

Family peruntukan (quick)

Family	Untuk	Bukan untuk
Micro Interaction	Toggle, toast, like, progress	Hero / scroll story
Hover & Interaction	Lift, press, magnetic, tilt	Page enter
Scroll-based	Sticky, horizontal, scroll-zoom	Button-only micro
Reveal & Wipe	Enter fades, split, mask, drawer	Endless loops as only motion
Text Motion	Word reveal, typewriter, marquee type	Forms / dense settings
Carousel & Continuous Flow	Marquee, filmstrip, snap	Single CTA focus pages
Grid Motion	Bento, flip grid, reflow	One-button chrome
Spotlight & Focus	Center stage, dim siblings	Whole-page noise
Stack & Scatter	Deck, fan, swipe deck	Admin tables
Hero Section Motion	Parallax / float device / aurora	App shell (max 1 signature)
Morph & Transform	Shared element, FAB morph	Every navigation
3D & Perspective	Orbit, coverflow	Default 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)