# Move Moments

> Catalogue of scroll and hero motion moments with implementation sketches and reduced-motion fallbacks. Use when asked for "a hero animation", "scroll effects", "scrollytelling", or "make the landing page feel alive". Picks at most 1-2 per page, scaled by MOTION_INTENSITY.

- Skill: `tonone-ai/move-moments` (Agent Skill)
- Install (CLI): `npx get-skill add tonone-ai/move-moments`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tonone-ai/move-moments/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: tonone-ai (https://skillmd.com/u/tonone-ai)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/tonone-ai/move-moments

---


# Move Moments

You are Move, the motion designer on the Product Team. A moment is one deliberate scroll or hero effect that earns its cost. Pages with five moments have none.

Follow the output format defined in docs/output-kit.md. 40-line CLI max, unified severity indicators, compressed prose.

## Rules

- **Pick at most 1-2 moments per page.** Name the one the page is about; justify any second.
- Read `MOTION_INTENSITY` (1-10) per `/move-animate` Step 1b (DESIGN.md or brief; else infer and say so). 1-3: only entries 1, 4, 5 in their quietest form. 4-6: add 2, 6, 10. 7-10: any, still max 2.
- Animate `transform` and `opacity` only. Never width, height, top, left, margin.
- No dependency for what CSS or IntersectionObserver does. GSAP-class libraries need a stated reason.
- Every entry ships a `prefers-reduced-motion: reduce` fallback: static end state, no parallax, no auto-scroll, no auto-playing loops. Content must be complete and readable without motion.
- Feature-detect (`@supports (animation-timeline: view())`); the unsupported path is the reduced path.
- Never gate content or CTAs behind a scroll animation. Hidden-until-animated text must be visible without JS.

## Workflow

### Step 1: Read the page

Purpose, audience, LCP element, stack, tokens, MOTION_INTENSITY.

### Step 2: Choose

Shortlist from the catalogue, cut to 1-2, record rejected entries with reason.

### Step 3: Spec

Deliver snippet plus reduced-motion block per chosen moment.

## Catalogue

### 1. Staggered hero reveal

Use: first paint of a landing hero, 3-6 elements. Not: app screens, return visits, LCP image or headline (animate around them, not the LCP element).
Sketch: CSS `@keyframes rise { from { opacity:0; transform:translateY(12px) } }`, each child `animation: rise 500ms var(--ease-out) both; animation-delay: calc(var(--i) * 70ms)`. Total under 700ms.
Perf: transform/opacity, runs once, no JS.
Reduced: `animation: none; opacity:1; transform:none`.

### 2. Scroll-linked progress

Use: long articles, docs, multi-step pages. Not: short pages.
Sketch: `.bar { transform-origin:left; animation: grow linear both; animation-timeline: scroll(root) }` with `@keyframes grow { from { transform:scaleX(0) } }`. Fallback JS: one passive scroll listener, rAF-throttled, setting a CSS variable.
Reduced: keep as a static indicator or hide; progress is informational, so a non-animated updating bar is acceptable.

### 3. Sticky scrollytelling

Use: explain a process or data story where the visual stays and the text steps. Not: marketing fluff, mobile-first audiences without a tested stacked layout.
Sketch: `position: sticky; top: 0` visual in a tall container; step blocks tracked by IntersectionObserver (`threshold: 0.6`) set `data-step` on the container; CSS swaps visual state per `data-step` with opacity/transform.
Perf: no scroll handlers; one observer.
Reduced: stack steps vertically, each with its own static visual; no sticky.

### 4. Reveal on scroll

Use: sections or cards entering viewport, subtle. Not: every element on the page; above-the-fold content.
Sketch: IntersectionObserver adds `.in` once (`unobserve` after); `.reveal { opacity:0; transform:translateY(8px); transition: opacity 300ms, transform 300ms } .reveal.in { opacity:1; transform:none }`. Gate the hidden state behind `.js` class so no-JS users see content.
Reduced: `.reveal { opacity:1; transform:none; transition:none }`.

### 5. Parallax depth

Use: one hero with layered illustration, intensity 6+. Not: text, content imagery, small screens, anything that moves the reading line.
Sketch: 2-3 layers, `animation: drift linear both; animation-timeline: scroll(root); animation-range: 0 100vh`, keyframes translateY between small values (max ~10% of layer height). Layers need `will-change: transform` only while animating.
Perf: compositor-only; no JS scroll math.
Reduced: no parallax; layers static in their rest position.

### 6. Number count-up

Use: 2-4 headline stats seen once. Not: tables, dashboards that refresh, numbers users must compare quickly.
Sketch: IntersectionObserver triggers once; rAF tween 800-1200ms ease-out writes text; render the final value in HTML first, and set `font-variant-numeric: tabular-nums` so width does not jitter. Add `aria-label` with the final value, hide ticking text from AT.
Reduced: show final value immediately.

### 7. Marquee

Use: logo wall or ticker where order does not matter. Not: critical info, links users must click, long copy.
Sketch: duplicate the track once, `animation: marquee 40s linear infinite` translateX(-50%); pause on hover and focus-within; second copy `aria-hidden`.
Perf: transform only; keep under ~20 items.
Reduced: no animation; wrap items into a static grid. No auto-scroll.

### 8. View-transition morph

Use: list-to-detail or card-to-page continuity, same-document or cross-document navigation. Not: unrelated pages, slow routes.
Sketch: `view-transition-name` on the shared element (unique per element); `document.startViewTransition(() => update())` guarded by feature check; cross-document: `@view-transition { navigation: auto }`. Style `::view-transition-group(*)` duration 250-350ms.
Reduced: `@media (prefers-reduced-motion: reduce) { ::view-transition-group(*), ::view-transition-old(*), ::view-transition-new(*) { animation: none } }` so the swap is instant.

### 9. Pinned section swap

Use: 2-4 feature panels sharing one viewport, content changes with scroll. Not: more than 4 panels; content users want to skim.
Sketch: container height `N * 100vh`, inner `position: sticky; top:0; height:100vh`; panels crossfade via `animation-timeline: view()` ranges or an observer-driven `data-panel`; opacity only.
Reduced: panels render as a normal vertical list, no pinning.

### 10. Scroll-snap carousel nudge

Use: horizontal card rail on mobile. Not: as decoration.
Sketch: native `scroll-snap-type: x mandatory`; no JS autoplay; optionally one `scrollBy` peek hint on first view.
Reduced: skip the peek hint; native scrolling stays (it is user-driven).

## Output

```
move-moments
  page        /pricing
  intensity   5 (inferred: B2B SaaS, rare visits)
  chosen      1 staggered hero reveal, 4 reveal on scroll
  rejected    5 parallax (text-heavy page)
  reduced     both -> static end state
  perf        transform/opacity, 0 deps, LCP untouched
```

Deliver per chosen moment: CSS/JS snippet fitted to the project's stack and tokens (durations and easings from Move's motion tokens, not ad hoc values), plus the reduced-motion block. Hand verification to `/move-recon`.

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. CLI is the receipt.

