@ericrisco/rsc 1.1.5 → 1.2.0

package/skills/animate-expo/references/recipes.md

@@ -1,385 +0,0 @@
-# Expo Animation Recipes
-
-Ready-to-build implementations for the cases that come up most in a React Native app. Start from the recipe, then adapt.
-
----
-
-## Setup the recipes assume
-
-```bash
-npx expo install react-native-reanimated react-native-worklets react-native-gesture-handler expo-haptics
-```
-
-(`react-native-keyboard-controller` only for the keyboard recipe.) `expo install`, not `npm install` — it resolves the versions that match the SDK. The worklets Babel plugin is configured by `babel-preset-expo` automatically.
-
-`GestureHandlerRootView` wraps the app once — in Expo Router, the root `_layout`:
-
-```jsx
-import { GestureHandlerRootView } from 'react-native-gesture-handler';
-
-export default function RootLayout() {
-  return (
-    <GestureHandlerRootView style={{ flex: 1 }}>
-      <Stack />
-    </GestureHandlerRootView>
-  );
-}
-```
-
-Imports and constants every recipe below shares:
-
-```js
-import { useState, useEffect, useMemo } from 'react';
-import Animated, {
-  useSharedValue, useAnimatedStyle, useAnimatedScrollHandler, useAnimatedReaction,
-  withSpring, withTiming, interpolate, Extrapolation, Easing,
-  FadeInDown, FadeOutDown, LinearTransition,
-} from 'react-native-reanimated';
-import { Gesture, GestureDetector } from 'react-native-gesture-handler';
-import { scheduleOnRN } from 'react-native-worklets';
-import * as Haptics from 'expo-haptics';
-
-const EASE_OUT = Easing.bezier(0.23, 1, 0.32, 1);      // strong ease-out for UI
-const EASE_IN_OUT = Easing.bezier(0.77, 0, 0.175, 1);  // on-screen movement
-const EASE_SHEET = Easing.bezier(0.32, 0.72, 0, 1);    // iOS sheet curve
-```
-
-Three conventions, explained once here instead of in every recipe:
-
-- **Shared values are read and written with `.get()` / `.set()`**, the form the Reanimated docs recommend for React Compiler support. `.value` still works, but the compiler can't see through it.
-- **`scheduleOnRN(fn, ...args)` replaces the deprecated `runOnJS(fn)(...args)`** for calling back to the React Native runtime from a worklet.
-- **Gestures are wrapped in `useMemo`.** Rebuilding a gesture on every render can reattach the recognizer and drop a drag that's mid-flight.
-
-**Gesture Handler v3:** Expo installs v2, and the recipes use its `Gesture.Pan()` builder. If the project is already on v3, the builder is legacy — each gesture is a hook taking one config object, with `onStart` → `onActivate`, `onEnd` → `onDeactivate`, and the `success` flag replaced by `event.canceled` (inverted). The hook manages its own identity, so drop the `useMemo`:
-
-```jsx
-const pan = usePanGesture({
-  activeOffsetY: [-10, 10],
-  onActivate: () => { context.set(translateY.get()); },
-  onUpdate: (e) => { translateY.set(context.get() + e.translationY); },
-  onDeactivate: (e) => { /* settle with withSpring as below */ },
-});
-```
-
----
-
-## Two worklets you'll need everywhere
-
-Momentum projection decides *where a flick was going*, so a fast short swipe commits and a slow long one doesn't. Rubber-banding makes a boundary resist instead of stopping dead.
-
-```js
-// Where the finger would come to rest if it kept decelerating.
-// Apple's exponential-decay form — not the v²/2a from physics class.
-function project(velocity, decelerationRate = 0.998) {
-  'worklet';
-  return ((velocity / 1000) * decelerationRate) / (1 - decelerationRate);
-}
-
-// The further past the edge, the less the element follows.
-function rubberband(overshoot, dimension, constant = 0.55) {
-  'worklet';
-  return (overshoot * dimension * constant) / (dimension + constant * Math.abs(overshoot));
-}
-```
-
----
-
-## Press feedback
-
-Every pressable in the app. This passes the frequency gate only because it's near-imperceptible: 120ms and a 3% scale is the ceiling for something touched this often — anything longer or larger belongs to rarer moments, per step 1 in SKILL.md. No gesture, no shared value — a CSS transition is the whole implementation.
-
-```jsx
-import Animated from 'react-native-reanimated';
-import { Pressable, StyleSheet } from 'react-native';
-
-function PressableScale({ onPress, children }) {
-  const [pressed, setPressed] = useState(false);
-  return (
-    <Pressable
-      onPress={onPress}
-      onPressIn={() => setPressed(true)}
-      onPressOut={() => setPressed(false)}
-      hitSlop={12}
-      pressRetentionOffset={16}
-    >
-      <Animated.View style={[styles.box, pressed && styles.pressed]}>{children}</Animated.View>
-    </Pressable>
-  );
-}
-
-const styles = StyleSheet.create({
-  box: {
-    transform: [{ scale: 1 }],
-    transitionProperty: 'transform',
-    transitionDuration: '120ms',
-    transitionTimingFunction: 'cubic-bezier(0.23, 1, 0.32, 1)',
-  },
-  pressed: { transform: [{ scale: 0.97 }] },
-});
-```
-
-`setState` is fine here — it fires twice per press, not per frame. `hitSlop` brings a small icon up to the 44pt target without growing it; `pressRetentionOffset` stops a slight finger drift from cancelling.
-
----
-
-## Bottom sheet you can drag to dismiss
-
-Before writing this: if the sheet is its own destination, use `presentation: 'formSheet'` (see **Screen transitions**) and get the platform's real sheet for free. Build this only when the sheet has to live inside an existing screen.
-
-```jsx
-const translateY = useSharedValue(0);
-const context = useSharedValue(0);
-
-const pan = useMemo(() => Gesture.Pan()
-  .activeOffsetY([-10, 10])   // let a horizontal swipe win; require intent before committing
-  .onStart(() => {
-    context.set(translateY.get());   // start from the current on-screen value, not from 0
-  })
-  .onUpdate((e) => {
-    const next = context.get() + e.translationY;
-    // downward is free; upward past the top resists
-    translateY.set(next >= 0 ? next : rubberband(next, HEIGHT));
-  })
-  .onEnd((e) => {
-    const projected = translateY.get() + project(e.velocityY);
-    if (projected > HEIGHT * 0.4) {
-      translateY.set(withSpring(HEIGHT, {
-        duration: 300, dampingRatio: 1, velocity: e.velocityY, overshootClamping: true,
-      }, (finished) => { if (finished) scheduleOnRN(onClose); }));
-    } else {
-      translateY.set(withSpring(0, { duration: 300, dampingRatio: 0.8, velocity: e.velocityY }));
-      scheduleOnRN(Haptics.impactAsync, Haptics.ImpactFeedbackStyle.Light);   // it snapped home
-    }
-  }), [onClose]);
-
-const sheetStyle = useAnimatedStyle(() => ({ transform: [{ translateY: translateY.get() }] }));
-```
-
-The four details that separate this from a bad drag:
-
-- **`onStart` captures the current value.** Without it, grabbing a sheet mid-animation teleports it — the animation must continue from where the eye last saw it.
-- **Velocity decides, not distance.** `project()` means a quick flick dismisses even a few pixels down. Requiring 40% travel makes the sheet feel heavy.
-- **Velocity is handed to the spring**, so there's no seam between the finger releasing and the animation continuing. This is the single detail that most separates "fluid" from "fine".
-- **`overshootClamping` on dismissal** — otherwise the sheet springs past the bottom of the screen and flashes a gap.
-
-The backdrop derives from the same value, so it's always in sync and costs nothing:
-
-```jsx
-const backdropStyle = useAnimatedStyle(() => ({
-  opacity: interpolate(translateY.get(), [0, HEIGHT], [1, 0], Extrapolation.CLAMP),
-}));
-```
-
----
-
-## Swipe to delete a row
-
-Before writing this: gesture-handler ships [`ReanimatedSwipeable`](https://docs.swmansion.com/react-native-gesture-handler/docs/components/reanimated_swipeable/), which already does swipe-to-reveal actions — thresholds, overshoot, open/close methods — on the UI thread. Reach for it when the row reveals action buttons. Build the gesture yourself only when the interaction is different in kind: swipe-to-commit with momentum projection, like this one.
-
-```jsx
-const x = useSharedValue(0);
-const context = useSharedValue(0);
-
-const pan = useMemo(() => Gesture.Pan()
-  .activeOffsetX([-10, 10])   // must declare the axis, or it fights the vertical scroll
-  .onStart(() => { context.set(x.get()); })   // grab mid-spring continues from where the row is, not from 0
-  .onUpdate((e) => { x.set(Math.min(0, context.get() + e.translationX)); })
-  .onEnd((e) => {
-    const projected = x.get() + project(e.velocityX);
-    if (projected < -SWIPE_THRESHOLD) {
-      x.set(withTiming(-WIDTH, { duration: 200, easing: EASE_OUT }, (f) => {
-        if (f) scheduleOnRN(onDelete, id);
-      }));
-    } else {
-      x.set(withSpring(0, { duration: 300, dampingRatio: 1, velocity: e.velocityX }));
-    }
-  }), [onDelete, id]);
-```
-
-Closing the gap the deleted row left is the list's job, not the row's:
-
-```jsx
-const ROW_CLOSE = LinearTransition.duration(200);   // module scope — builders rebuilt in render cost every re-render
-
-<Animated.FlatList data={items} itemLayoutAnimation={ROW_CLOSE} ... />
-```
-
-`activeOffsetX` is the mobile-specific part. A pan handler inside a scroll view with no axis declared will steal vertical scrolls, and the list will feel broken in a way that looks like a scrolling bug rather than a gesture bug.
-
----
-
-## Collapsing header on scroll
-
-```jsx
-const scrollY = useSharedValue(0);
-const onScroll = useAnimatedScrollHandler((e) => { scrollY.set(e.contentOffset.y); });
-
-const titleStyle = useAnimatedStyle(() => ({
-  opacity: interpolate(scrollY.get(), [0, 60], [1, 0], Extrapolation.CLAMP),
-  transform: [{ translateY: interpolate(scrollY.get(), [0, 60], [0, -12], Extrapolation.CLAMP) }],
-}));
-
-<Animated.ScrollView onScroll={onScroll} scrollEventThrottle={16}>
-```
-
-**Never animate the header's `height` to collapse it.** That runs a layout pass on the header and everything below it on every scroll frame — the one animation guaranteed to stutter, because it's competing with the scroll itself. Give the container a fixed height and translate the content inside it, clipping with `overflow: 'hidden'`.
-
-`Extrapolation.CLAMP` is not optional: without it, scrolling past 60 keeps driving opacity negative and the header reappears inverted at the bottom of a long list.
-
----
-
-## List entrances
-
-```jsx
-// The Reanimated docs recommend building layout animations outside components,
-// or in useMemo — an inline chain in JSX rebuilds the builder on every render.
-// A per-index delay can't live at module scope, so the row memoizes its own:
-function Row({ item, index }) {
-  const entering = useMemo(() => FadeInDown.duration(250).delay(index * 40), [index]);
-  return <Animated.View entering={entering}>{/* ... */}</Animated.View>;
-}
-
-{items.map((item, i) => <Row key={item.id} item={item} index={i} />)}
-```
-
-Stagger 30–80ms. Longer feels slow, shorter reads as simultaneous.
-
-**Never put `entering` on a row inside `FlatList`, `FlashList`, or any virtualized list.** Rows are recycled, so the animation re-fires every time one scrolls back into view — the list appears to flicker while the user scrolls. Animate the list container once on mount, or use `itemLayoutAnimation` for reflow only.
-
-Entrance animations are for content the user asked for and is waiting on. A list they scroll past all day should already be there.
-
----
-
-## Keyboard-synced UI
-
-Needs its own module and a one-time provider ([Expo keyboard guide](https://docs.expo.dev/guides/keyboard-handling/)):
-
-```bash
-npx expo install react-native-keyboard-controller
-```
-
-```jsx
-import { KeyboardProvider } from 'react-native-keyboard-controller';
-
-// Root _layout, next to GestureHandlerRootView — hooks below do nothing without it.
-<KeyboardProvider>
-  <Stack />
-</KeyboardProvider>
-```
-
-```jsx
-import { useReanimatedKeyboardAnimation } from 'react-native-keyboard-controller';
-
-const { height } = useReanimatedKeyboardAnimation();   // 0 → -keyboardHeight, on the UI thread
-const footerStyle = useAnimatedStyle(() => ({ transform: [{ translateY: height.get() }] }));
-```
-
-Never build this from `Keyboard.addListener` plus a timing animation. The keyboard rides a private system curve, the event arrives on the JS thread after the keyboard has already started moving, and any duration you pick will visibly lag or lead it. The UI must be driven by the keyboard's actual position, frame by frame.
-
----
-
-## Tab / segmented indicator
-
-Measure once, then animate transforms.
-
-```jsx
-const [layouts, setLayouts] = useState({});   // measured with onLayout, not per frame
-const x = useSharedValue(0);
-const w = useSharedValue(0);
-
-useEffect(() => {
-  const l = layouts[active];
-  if (!l) return;
-  x.set(withTiming(l.x, { duration: 250, easing: EASE_IN_OUT }));
-  w.set(withTiming(l.width, { duration: 250, easing: EASE_IN_OUT }));
-}, [active, layouts]);
-
-const pillStyle = useAnimatedStyle(() => ({
-  transform: [{ translateX: x.get() }],
-  width: w.get(),
-}));
-```
-
-This is the sanctioned `width` animation: the pill is absolutely positioned with no children, so nothing else re-lays-out, and its corner radius survives — `scaleX` would smear the corners into ovals.
-
-`ease-in-out`, because the pill is moving across the screen rather than entering or leaving it. Fire `Haptics.selectionAsync()` on the press, not when the pill lands.
-
----
-
-## Screen transitions (Expo Router)
-
-Configure the native stack. Never rebuild a screen transition in JS: the native one runs on the platform side, keeps the interactive back gesture, and matches every other app on the device.
-
-```jsx
-<Stack screenOptions={{ animation: reduced ? 'fade' : 'default' }}>
-  <Stack.Screen name="settings" options={{ animation: 'slide_from_right', animationMatchesGesture: true }} />
-  <Stack.Screen name="compose" options={{ presentation: 'modal' }} />
-  <Stack.Screen name="filter" options={{
-    presentation: 'formSheet',
-    sheetAllowedDetents: 'fitToContents',
-    sheetGrabberVisible: true,
-  }} />
-</Stack>
-```
-
-| Navigation | Option |
-| --- | --- |
-| Deeper into a hierarchy | `animation: 'default'` — the platform push, unmodified |
-| A self-contained task the user can abandon | `presentation: 'modal'` |
-| A short interruption: picker, filter, share | `presentation: 'formSheet'` with detents |
-| Between tabs | `animation: 'none'` |
-| Reduced motion | `animation: 'fade'` |
-
-`animationMatchesGesture: true` makes the iOS back swipe run your transition in reverse under the finger, instead of the default push. Set it whenever you set a custom `animation`, or dragging back looks like a different app than pushing forward.
-
-`formSheet` is native on both platforms, but not the same on both — the [Expo modal docs](https://docs.expo.dev/router/advanced/modals/#form-sheet-presentation) have the full list:
-
-- **Android caps detents at three.** A longer `sheetAllowedDetents` array works on iOS and silently truncates on Android — design for three.
-- **`sheetGrabberVisible` is iOS-only.** Android shows no grabber; don't rely on it as the only "this is draggable" affordance.
-- **Android form sheets can't host native headers or nested stacks.** Keep the sheet's content a single screen; if it needs its own navigation, use `presentation: 'modal'` instead.
-- **`fitToContents` needs explicitly sized content.** A `flex: 1` root has no intrinsic height to fit — size the content, or the detent is wrong.
-
----
-
-## Toast
-
-```jsx
-// Module scope — layout-animation builders live outside the component.
-const TOAST_ENTER = FadeInDown.duration(300).easing(EASE_OUT);
-const TOAST_EXIT = FadeOutDown.duration(250).easing(EASE_OUT);
-
-<Animated.View
-  entering={TOAST_ENTER}
-  exiting={TOAST_EXIT}
-  style={{ position: 'absolute', bottom: insets.bottom + 16, left: 16, right: 16 }}
-/>
-```
-
-- **The 300ms cap holds here too.** A toast isn't an exception — it's uninvited, so if anything it should be quicker and quieter than motion the user asked for.
-- **It exits the way it entered.** Entering from the bottom and leaving to the side reads as two unrelated elements.
-- **Exit ~20% faster than entry.** The user has finished reading; the arrival deserves the time, the departure doesn't.
-- **Safe area insets, always.** A toast at `bottom: 16` sits under the home indicator on every modern iPhone.
-
-If toasts stack and the list reflows, add `itemLayoutAnimation` and expect to tune the opacity against the reflow by eye — there's no formula for that pair. Look at it again the next day.
-
----
-
-## Firing something once at a threshold
-
-When a crossing point matters — a detent, a snap, a pull-to-refresh arming — don't poll it from JS and don't `scheduleOnRN` every frame.
-
-```jsx
-const armed = useSharedValue(false);
-
-useAnimatedReaction(
-  () => pullDistance.get() > REFRESH_THRESHOLD,
-  (isArmed, wasArmed) => {
-    if (isArmed !== wasArmed) {
-      armed.set(isArmed);
-      scheduleOnRN(Haptics.impactAsync, Haptics.ImpactFeedbackStyle.Light);
-    }
-  }
-);
-```
-
-The comparison runs on the UI thread every frame; the JS call happens twice per pull. That's the pattern for every "do something when the animation reaches X".

package/skills/animation-vocabulary/SKILL.md

@@ -1,189 +0,0 @@
----
-name: animation-vocabulary
-description: "Reverse glossary: turn a vague description of a motion effect into its exact name — a popover growing from its trigger is origin-aware, iOS overscroll is rubber-banding, items appearing one after another with a delay is a stagger. Use for \"what's it called when…\" or \"what do you call it when…\"."
-tags: [motion, animation, glossary, terminology, naming]
-recommends: [animate, apple-design]
-profiles: [full]
-origin: emilkowalski (MIT, adapted)
----
-
-# Animation Vocabulary
-
-Turn a vague description of a motion or effect into the precise term, so the user knows what to ask for.
-
-## Quick Start
-
-The user describes an effect loosely. You return the matching term(s) in this format:
-
-```
-**Stagger** — Animate several items one after another with a small delay between each, creating a cascade.
-```
-
-If several terms could fit, list the best match first, then 1–2 alternates with a one-line note on how they differ.
-
-## Instructions
-
-1. **Read for intent, not keywords.** Users describe what they *see* or *feel* ("springy", "slides off", "draws itself in"), not the technical name. Map the sensation to the glossary below.
-2. **Quote the glossary verbatim.** Its descriptions are authoritative — use them as-is, don't paraphrase.
-3. **Disambiguate close terms.** When two compete (*Clip-path* vs *Mask*, *Pop in* vs *Bounce*, *Shared element transition* vs *Layout animation*), contrast them so the user can pick.
-4. **When nothing matches exactly,** name the closest term and say plainly it's an approximation, or describe the effect in the glossary's vocabulary (e.g. "that's a *stagger* of *scale-in* entrances").
-5. **Stay within this glossary.** If a term genuinely isn't here, say so rather than inventing one — though you may explain the concept using these words.
-6. **Keep it tight.** A naming question wants a name, not an essay. Lead with the term; expand only if asked.
-
-## Examples
-
-**Example 1 — feel-based**
-User: "What's it called when a popover seems to grow out of the button you clicked instead of from its middle?"
-Output:
-```
-**Origin-aware animation** — An element animates out of its trigger, like a popover growing from the button that opened it instead of from its own center which is the default in CSS.
-```
-
-**Example 2 — disambiguation**
-User: "The thing where one image turns into another image."
-Output:
-```
-**Morph** — One shape smoothly turns into another shape, e.g. Dynamic Island.
-
-Close alternates:
-- **Crossfade** — if they simply fade over each other in the same spot.
-- **Shared element transition** — if an element travels and transforms from one position into another.
-```
-
-**Example 3 — physics feel**
-User: "That iOS scroll where it resists and snaps back when you pull too far."
-Output:
-```
-**Rubber-banding** — Resistance and snap-back when you drag past a boundary (the iOS overscroll feel).
-```
-
-## Glossary
-
-_Adapted from the vocabulary page at [animations.dev](https://animations.dev/) (MIT). It is a
-snapshot, not a live mirror: this catalog does not control that page, so treat any drift as the
-upstream page being newer — and stay inside this glossary rather than inventing a term._
-
-### Entrances & Exits — how elements appear and disappear
-- **Fade in / Fade out** — Element appears or disappears by changing opacity.
-- **Slide in** — Element enters by sliding in from off-screen (left, right, top, or bottom).
-- **Scale in** — Element grows from smaller to full size as it appears, often paired with a fade.
-- **Pop in** — Element appears with a slight overshoot, like it bounces into place.
-- **Reveal** — Content is uncovered gradually, often by animating a clip-path or mask.
-- **Enter / Exit** — The animation an element plays when it's added to or removed from the screen.
-
-### Sequencing & Timing — coordinating multiple elements or moments
-- **Keyframes** — Defined points in an animation (0%, 50%, 100%) that the browser fills the gaps between.
-- **Interpolation / Tween** — Generating all the in-between frames between a start and end value, so motion is continuous.
-- **Stagger** — Animate several items one after another with a small delay between each, creating a cascade.
-- **Orchestration** — Deliberately timing multiple animations so they feel like one coordinated motion.
-- **Delay** — Time before an animation starts.
-- **Duration** — How long an animation takes.
-- **Fill mode** — Whether an element keeps its first or last frame's styles before the animation starts or after it ends (e.g. forwards).
-- **Stepped animation** — An animation that is divided into discrete steps, like a countdown timer.
-
-### Movement & Transforms — changing an element's position, size, or angle
-- **Translate** — Move an element along the X or Y axis.
-- **Scale** — Make an element bigger or smaller.
-- **Rotate** — Spin an element around a point.
-- **Skew** — Slant an element along the X or Y axis, shearing it out of its rectangular shape.
-- **3D tilt / Flip** — Rotate in 3D space (rotateX / rotateY) to add depth.
-- **Perspective** — How strong the 3D effect looks — a lower value exaggerates depth, like the viewer is closer.
-- **Transform origin** — The anchor point a scale or rotation grows or spins from.
-- **Origin-aware animation** — An element animates out of its trigger, like a popover growing from the button that opened it instead of from its own center which is the default in CSS.
-
-### Transitions Between States — connecting one state, view, or element to another
-- **Crossfade** — One element fades out as another fades in, in the same spot.
-- **Continuity transition** — A change that keeps the user oriented by visually connecting before and after. For example, making the same rectangle bigger and smaller.
-- **Morph** — One shape smoothly turns into another shape, e.g. Dynamic Island.
-- **Shared element transition** — An element travels and transforms from one position into another, like a thumbnail expanding into a card.
-- **Layout animation** — When an element's size or position changes, it animates to the new spot instead of snapping.
-- **Accordion / Collapse** — A section smoothly expands and collapses its height to show or hide content.
-- **Direction-aware transition** — Content slides one way going forward and the opposite way going back, so navigation has a sense of direction.
-
-### Scroll — motion tied to scrolling or navigating between views
-- **Scroll reveal** — Elements fade or slide into place as they enter the viewport.
-- **Scroll-driven animation** — An animation whose progress is tied directly to scroll position.
-- **Parallax** — Background and foreground move at different speeds while scrolling, creating depth.
-- **Page transition** — An animation that plays when navigating from one page or route to another.
-- **View transition** — The browser morphs between two states or pages, connecting shared elements.
-
-### Feedback & Interaction — responding to the user's actions
-- **Hover effect** — Visual change when the cursor moves over an element.
-- **Press / Tap feedback** — A subtle scale-down when an element is clicked, so it feels physical.
-- **Hold to confirm** — A progress effect that fills up while the user holds a button.
-- **Drag** — Moving an element by grabbing it, often with momentum when released.
-- **Drag to reorder** — Dragging items in a list to rearrange them, while the others shift to make room.
-- **Swipe to dismiss** — Dragging an element off-screen to close it, like a drawer or toast.
-- **Rubber-banding** — Resistance and snap-back when you drag past a boundary (the iOS overscroll feel).
-- **Shake / Wiggle** — A quick side-to-side jitter signaling an error or rejected input.
-- **Ripple** — A circle expanding from the point of a tap, confirming the press.
-
-### Easing — how speed changes over an animation
-- **Easing** — The rate at which an animation speeds up or slows down.
-- **Ease-out** — Starts fast, ends slow. The default for most UI and anything responding to the user.
-- **Ease-in** — Starts slow, ends fast. Usually avoided; can feel sluggish.
-- **Ease-in-out** — Slow, fast, slow. Good for elements already on screen moving from A to B.
-- **Linear** — Constant speed. Avoid for UI; reserve for spinners or marquees.
-- **Cubic-bezier** — A custom easing curve you define for precise control.
-- **Asymmetric easing** — A curve that accelerates and decelerates at different rates. Feels more alive than a symmetric one.
-
-### Spring Animations — physics-based motion as an alternative to fixed-duration easing
-- **Spring** — Motion driven by physics (tension, mass, damping) rather than a set duration.
-- **Stiffness / Tension** — How strongly the spring pulls toward its target. Higher feels snappier.
-- **Damping** — How quickly a spring settles. Lower damping means more bounce and oscillation.
-- **Mass** — How heavy the animated element feels. More mass makes it slower and more sluggish.
-- **Bounce** — A spring that overshoots and settles, adding playfulness.
-- **Perceptual duration** — How long a spring feels finished, even though it keeps micro-settling underneath.
-- **Momentum** — Motion that carries velocity, especially after a drag or interruption.
-- **Velocity** — How fast and in which direction an element is moving. A spring carries it into the next animation when interrupted, so a flicked element keeps its speed.
-- **Interruptible animation** — An animation that can be smoothly redirected mid-flight instead of finishing first.
-
-### Looping & Ambient Motion — animations that run on their own
-- **Marquee** — Text or content that scrolls continuously in a loop.
-- **Loop** — An animation that repeats, a set number of times or infinitely.
-- **Alternate (yoyo)** — A loop that plays forward then reverses each iteration, instead of jumping back to the start.
-- **Orbit** — An element circling around another in a continuous path.
-- **Pulse** — A gentle repeating scale or opacity change to draw attention.
-- **Float** — A gentle, continuous up-and-down drift that makes a static element feel alive and weightless.
-- **Idle animation** — Subtle motion that plays while an element is just sitting there, waiting to be interacted with.
-
-### Polish & Effects — the small touches that separate good from great
-- **Blur** — A blur filter used to soften an element or mask tiny imperfections.
-- **Clip-path** — Clipping an element to a shape, used for reveals, masks, and before/after sliders.
-- **Mask** — Hiding or revealing parts of an element using a shape or gradient — like clip-path, but with soft, fadeable edges.
-- **Before / after slider** — A draggable divider that wipes between two overlaid images to compare them.
-- **Line drawing** — An SVG path that draws itself in, like an invisible pen tracing it.
-- **Text morph** — Text that animates character by character when it changes, drawing attention to the new value.
-- **Skeleton / Shimmer** — A placeholder with a moving sheen shown while content loads.
-- **Number ticker** — Digits rolling or counting up to a value.
-- **Tabular numbers** — Fixed-width digits so numbers don't shift around as they change. Essential for tickers, timers, and counters.
-- **Typewriter** — Text appearing one character at a time, as if being typed.
-
-### Performance — what keeps motion smooth instead of stuttering
-- **Frame rate (FPS)** — Frames drawn per second. 60fps is the baseline for smooth motion; 120fps on newer displays.
-- **Jank** — Visible stutter when the browser drops frames because it can't keep up with the animation.
-- **Dropped frame** — A frame the browser missed its deadline to draw, causing a tiny hitch in motion.
-- **Compositing** — Letting the GPU move or fade an element on its own layer without redoing layout or paint.
-- **will-change** — A CSS hint that an element is about to animate, so the browser can promote it to its own layer ahead of time.
-- **Layout thrashing** — Animating properties like width, height, top, or left that force the browser to recalculate layout every frame, causing jank.
-
-### Principles to Know — concepts that guide when and how to animate
-- **Purposeful animation** — Motion should serve a function — orient, give feedback, show relationships — not just decorate.
-- **Anticipation** — A small wind-up in the opposite direction before a move, hinting at what's about to happen.
-- **Follow-through** — Parts of an element keep moving and settle slightly after the main motion stops, adding weight.
-- **Squash & stretch** — Deforming an element as it moves to convey weight, speed, and flexibility.
-- **Perceived performance** — The right animation makes an interface feel faster, even when it isn't.
-- **Frequency of use** — The more often a user sees an animation, the shorter and subtler it should be.
-- **Spatial consistency** — Animating so an element keeps its identity and position across states, so users never lose track of where things went.
-- **Hardware acceleration** — Animating transform and opacity lets the GPU keep motion smooth.
-- **Reduced motion** — Respecting the user's prefers-reduced-motion setting by toning down or removing motion.
-
----
-
-## Credit
-
-Adapted for the rsc catalog from **[emilkowalski/skills](https://github.com/emilkowalski/skills)**
-(MIT, commit `d23d7f8`) by Emil Kowalski — the design-engineering and animation philosophy behind
-[Sonner](https://sonner.emilkowal.ski), [Vaul](https://vaul.emilkowal.ski) and
-[animations.dev](https://animations.dev). The craft bar here is his; the routing, gates and evals
-that make it an rsc skill are not. Nothing in this body is a substitute for his course.

package/skills/animation-vocabulary/evals/cases.yaml

@@ -1,31 +0,0 @@
-skill: animation-vocabulary
-
-should_trigger:
-  - prompt: "What's it called when a popover seems to grow out of the button you clicked instead of from its middle?"
-    why: "A naming question answered by a specific glossary term (origin-aware animation)."
-  - prompt: "What's the name for that iOS scroll that resists and snaps back when you pull too far?"
-    why: "Rubber-banding; a feel-based description mapped to the exact term."
-  - prompt: "What do you call it when items appear one after another with a small delay?"
-    why: "Stagger; the canonical reverse-lookup case."
-  - prompt: "I want to describe an effect to a designer but I don't know the right word for it."
-    why: "The skill's stated purpose: give the user the vocabulary to prompt with."
-  - prompt: "Is the thing where one image turns into another called a morph or a crossfade?"
-    why: "Disambiguation between two close terms, which the skill handles explicitly."
-
-should_not_trigger:
-  - prompt: "Build me that origin-aware popover animation."
-    route_to: "animate"
-    why: "Naming is done; this is implementation."
-  - prompt: "Explain the physics of springs — damping, response, velocity handoff."
-    route_to: "apple-design"
-    why: "The mechanism and its values, not the name of an effect."
-  - prompt: "Review whether the stagger delay in this list is right."
-    route_to: "review-animations"
-    why: "A judgement on existing motion, not a naming question."
-  - prompt: "Translate our UI copy into Catalan."
-    route_to: "translation-l10n"
-    why: "Also a words-and-terms request, but a different domain entirely."
-
-capability:
-  - scenario: "User describes an effect that is not in the glossary: 'the thing where the whole page melts into liquid when you click'."
-    expect: "Says plainly that no glossary term matches rather than inventing one, then describes the effect using the glossary's own vocabulary (for example a morph plus a mask reveal), and stays inside the curated list."