@ericrisco/rsc 1.1.5 → 1.1.6

package/skills/animate/evals/cases.yaml

@@ -1,36 +0,0 @@
-skill: animate
-
-should_trigger:
-  - prompt: "Animate this dropdown so it opens smoothly — pick the right easing and duration."
-    why: "A build request for a named component's motion: the skill's core use case."
-  - prompt: "Add a transition when the modal opens and closes so it doesn't just pop in."
-    why: "Building an enter/exit animation, including the exit path the skill insists is symmetric."
-  - prompt: "Make this button feel responsive when you press it."
-    why: "Press feedback is a recipe in this skill; 'feel responsive' is its vocabulary."
-  - prompt: "I want a hold-to-delete button where the fill animates while you hold it."
-    why: "Hold-to-confirm is an explicit recipe (clip-path, 2s linear press, snappy release)."
-  - prompt: "Add motion to this toast so it slides in from the bottom and can be swiped away."
-    why: "Toast motion with a gesture: transitions over keyframes, symmetric exit, velocity dismissal."
-  - prompt: "Make this list of cards feel alive when the page loads."
-    why: "'Feel alive' is named in the description; the answer is a stagger, or a refusal if the frequency tier is wrong."
-
-should_not_trigger:
-  - prompt: "Review the animations in this pull request and tell me what's wrong with them."
-    route_to: "review-animations"
-    why: "Critiquing existing motion, not building it."
-  - prompt: "Animate this bottom sheet in our Expo app so the drag feels native on Android."
-    route_to: "animate-expo"
-    why: "React Native / Expo motion: different runtime, different tools, no hover."
-  - prompt: "What could be animated in this dashboard? I don't know where motion would help."
-    route_to: "find-animation-opportunities"
-    why: "Nothing has been chosen yet; this is a search, not a build."
-  - prompt: "What's the term for when a popover grows out of the button you clicked?"
-    route_to: "animation-vocabulary"
-    why: "A naming question, not an implementation."
-  - prompt: "Choose the color palette and spacing scale for this landing page."
-    route_to: "design"
-    why: "Visual system, no motion involved."
-
-capability:
-  - scenario: "User asks: 'animate the command palette so it fades in when you hit Cmd+K'."
-    expect: "Refuses the animation on frequency grounds — a keyboard-initiated, 100+/day action gets no motion — says so plainly, and offers the instant state change instead. Producing zero lines of animation code here is the correct outcome."

package/skills/animate/references/recipes.md

@@ -1,324 +0,0 @@
-# Animation Recipes
-
-Ready-to-build implementations for the cases that come up most. Start from the recipe, then adapt — don't rebuild from scratch.
-
-Curves are the `--ease-out`, `--ease-in-out`, and `--ease-drawer` tokens defined in SKILL.md.
-
----
-
-## Button press
-
-Any pressable element. Instant feedback that the interface heard the user.
-
-```css
-.button {
-  transition: transform 160ms var(--ease-out);
-}
-
-.button:active {
-  transform: scale(0.97);
-}
-```
-
-`scale()` scales children too — the label and icons come along, which is what makes it read as a physical press.
-
-No hover gating needed here: `:active` is a real press on touch. Gate any `:hover` styling separately.
-
----
-
-## Dropdown, popover, menu, select
-
-Scales out of its trigger, not out of thin air.
-
-```css
-.popover {
-  transform-origin: var(--transform-origin); /* Base UI supplies this */
-  transition:
-    opacity 200ms var(--ease-out),
-    transform 200ms var(--ease-out);
-}
-
-.popover[data-starting-style],
-.popover[data-ending-style] {
-  opacity: 0;
-  transform: scale(0.95);
-}
-```
-
-The `transform-origin` is the whole point — the panel should look like it came out of the thing you clicked.
-
----
-
-## Tooltip
-
-Same shape as a popover, faster, plus the detail most implementations miss.
-
-```css
-.tooltip {
-  transform-origin: var(--transform-origin);
-  transition:
-    transform 125ms var(--ease-out),
-    opacity 125ms var(--ease-out);
-}
-
-.tooltip[data-starting-style],
-.tooltip[data-ending-style] {
-  opacity: 0;
-  transform: scale(0.97);
-}
-
-/* Once one tooltip is open, neighbours open instantly */
-.tooltip[data-instant] {
-  transition-duration: 0ms;
-}
-```
-
-The initial delay prevents accidental activation. After that, skipping both the delay and the animation makes the whole toolbar feel faster.
-
----
-
-## Modal
-
-The one popover that stays centered.
-
-```css
-.modal {
-  transform-origin: center; /* exempt — not anchored to a trigger */
-  transition:
-    opacity 250ms var(--ease-out),
-    transform 250ms var(--ease-out);
-}
-
-.modal[data-starting-style],
-.modal[data-ending-style] {
-  opacity: 0;
-  transform: scale(0.96);
-}
-
-.backdrop {
-  transition: opacity 250ms var(--ease-out);
-}
-```
-
-Animate the backdrop's opacity alongside it so they read as one surface.
-
----
-
-## Drawer / sheet
-
-```css
-.drawer {
-  transform: translateY(0);
-  transition: transform 500ms var(--ease-drawer);
-}
-
-.drawer[data-closed] {
-  transform: translateY(100%);
-}
-```
-
-This is how Vaul hides a drawer before animating it in.
-
-Add drag and it becomes a gesture problem — see **Drag to dismiss** below.
-
----
-
-## Toast
-
-```css
-.toast {
-  opacity: 1;
-  transform: translateY(0);
-  transition:
-    opacity 400ms ease,
-    transform 400ms ease;
-
-  @starting-style {
-    opacity: 0;
-    transform: translateY(100%);
-  }
-}
-```
-
-- `ease` rather than `ease-out`, slightly slower than typical UI: Sonner reads as elegant partly because its motion is tuned to the component's personality rather than to the generic UI budget.
-- If `@starting-style` isn't available, fall back to the mount flag:
-
-```jsx
-useEffect(() => { setMounted(true); }, []);
-// <div data-mounted={mounted}>
-```
-
-When toasts stack and the list reflows, the opacity change has to work against the height change. There's no formula for that pair — adjust until it feels right, then check it again the next day.
-
----
-
-## Accordion / collapse
-
-```css
-.content {
-  overflow: hidden;
-  transition:
-    height 200ms var(--ease-out),
-    opacity 200ms var(--ease-out);
-}
-```
-
-Keep it short — this is one of the few animations that costs layout on every frame, so a long duration is expensive as well as sluggish. Measure the content height in JS (or use a headless primitive that supplies it) rather than animating to `auto`.
-
----
-
-## Stagger a group entrance
-
-For a list or grid the user sees occasionally — not for a list they scroll past all day.
-
-```css
-.item {
-  opacity: 0;
-  transform: translateY(8px);
-  animation: fadeIn 300ms var(--ease-out) forwards;
-}
-
-.item:nth-child(2) { animation-delay: 50ms; }
-.item:nth-child(3) { animation-delay: 100ms; }
-.item:nth-child(4) { animation-delay: 150ms; }
-
-@keyframes fadeIn {
-  to {
-    opacity: 1;
-    transform: translateY(0);
-  }
-}
-```
-
-Stagger is decorative — it must never block interaction while it plays.
-
----
-
-## Hold to confirm
-
-For destructive actions where a plain click is too easy to fire by accident.
-
-```css
-.overlay {
-  clip-path: inset(0 100% 0 0);
-  transition: clip-path 200ms var(--ease-out); /* release: snappy */
-}
-
-.button:active .overlay {
-  clip-path: inset(0 0 0 0);
-  transition: clip-path 2s linear;             /* press: slow and deliberate */
-}
-
-.button:active {
-  transform: scale(0.97);
-}
-```
-
-`linear` is correct here — the fill is a progress indicator, and progress shouldn't ease.
-
----
-
-## Tab indicator with a color transition
-
-Timing individual color transitions across a tab list never quite lands. Clip instead.
-
-Duplicate the tab list. Style the copy as the active state — different background, different text color. Clip the copy so only the active tab shows, and animate the clip on change:
-
-```css
-.tabs-active-copy {
-  clip-path: inset(0 60% 0 20%); /* driven by the active tab's position */
-  transition: clip-path 250ms var(--ease-in-out);
-}
-```
-
-The text and background change together, in perfect sync, because they're one element being revealed rather than two colors being interpolated.
-
----
-
-## Scroll reveal
-
-Marketing surfaces only. Don't do this to functional UI a user visits daily.
-
-```css
-.reveal {
-  clip-path: inset(0 0 100% 0);
-  transition: clip-path 600ms var(--ease-in-out);
-}
-
-.reveal[data-visible] {
-  clip-path: inset(0 0 0 0);
-}
-```
-
-Trigger with `IntersectionObserver`, or Motion's `useInView` with `{ once: true, margin: "-100px" }`. Fire it once — re-animating on every scroll-by is an interface fighting its reader.
-
----
-
-## Drag to dismiss
-
-The gesture recipe. Springs, not durations, because the user can reverse mid-motion.
-
-```js
-// Dismiss on a flick, not just on distance
-const timeTaken = Date.now() - dragStartTime.current;
-const velocity = Math.abs(swipeAmount) / timeTaken;
-
-if (Math.abs(swipeAmount) >= SWIPE_THRESHOLD || velocity > 0.11) {
-  dismiss();
-}
-```
-
-```js
-// Set transform on the dragged element directly.
-// Driving it through a CSS variable on the parent recalcs styles for every child.
-element.style.transform = `translateY(${distance}px)`;
-```
-
-Four details that separate a good drag from a bad one:
-
-- **Pointer capture** once the drag starts, so it continues when the pointer leaves the element's bounds.
-- **Multi-touch protection** — `if (isDragging) return` on new touch points, or switching fingers mid-drag makes the element jump.
-- **Damping past boundaries** — dragging beyond a natural edge moves the element less the further it goes. Real things slow before they stop.
-- **Friction, not a wall** — allow the over-drag with rising resistance rather than refusing it.
-
-Settle with a spring so an interrupted drag keeps its velocity:
-
-```js
-{ type: "spring", duration: 0.5, bounce: 0.2 }
-```
-
----
-
-## Masking a crossfade that won't settle
-
-When two states overlap visibly during a transition and no amount of easing or duration tuning fixes it, blur the seam:
-
-```css
-.content {
-  transition:
-    filter 200ms ease,
-    opacity 200ms ease;
-}
-
-.content.transitioning {
-  filter: blur(2px);
-  opacity: 0.7;
-}
-```
-
-Without blur the eye reads two distinct objects swapping. Blur blends them into one perceived transformation. Keep it under 20px — heavy blur is expensive, especially in Safari.
-
----
-
-## Programmatic, without a library
-
-When the motion needs JS control but not a dependency, WAAPI gives you CSS-grade performance:
-
-```js
-element.animate(
-  [{ clipPath: 'inset(0 0 100% 0)' }, { clipPath: 'inset(0 0 0 0)' }],
-  { duration: 1000, fill: 'forwards', easing: 'cubic-bezier(0.77, 0, 0.175, 1)' }
-);
-```
-
-Hardware-accelerated, interruptible, no bundle cost.

package/skills/animate-expo/SKILL.md

@@ -1,281 +0,0 @@
----
-name: animate-expo
-description: "Build animation and gestures in React Native and Expo with Reanimated worklets on the UI thread — sheets, drawers, screen transitions, swipe, drag, press feedback, haptics. Use when adding gestures to an Expo app, or when motion stutters, janks or drops frames on a real Android or iOS device."
-tags: [motion, animation, expo, react-native, gestures]
-recommends: [expo, react-native, animate]
-profiles: [full]
-origin: emilkowalski (MIT, adapted)
----
-
-# Building Animations in Expo
-
-> **SDD gate.** If this fired on a **new, non-trivial feature or behaviour change** and there is
-> **no approved spec + plan** under `02-DOCS/wiki/sdd/`, hand off to `../specify/SKILL.md` first —
-> it runs brainstorm → spec → plan → tasks before any code, then routes back here once the plan is
-> approved. Build straight from here only for a genuinely one-line / low-risk change, or a bug fix
-> restoring intended behaviour. Method: `../sdd/SKILL.md`.
-
-**Hand-offs.** Web motion is `../animate/SKILL.md`'s — this file exists because mobile changes the
-three things listed above. The **Expo platform** itself (router, config plugins, EAS, native modules,
-store builds) is `../expo/SKILL.md`'s, and bare React Native app structure is
-`../react-native/SKILL.md`'s: both own the app, this one owns its motion. Gesture *physics* as a
-discipline — momentum projection, rubber-banding, velocity handoff — is `../apple-design/SKILL.md`'s.
-
-A construction skill for React Native. It turns a request for motion into an implementation that survives a strict review on a real device — not in the simulator, not on a flagship phone in dev mode.
-
-Mobile changes three things about animation, and everything in this skill follows from them:
-
-1. **There is no hover.** Every affordance the web puts in hover has to live in press, position, or nothing.
-2. **There are two runtimes.** Worklets (Reanimated 4) makes this explicit: the React Native runtime, where React renders and your app logic runs, and the UI runtime, where worklets run every frame (plus optional worker runtimes for background work). An animation that touches the RN runtime stutters the moment the app does anything else. The whole craft is keeping motion on the UI runtime.
-3. **The user's finger is on the element.** Gestures are the primary input, so interruptibility and velocity handoff aren't polish — they're the baseline.
-
-## Operating Posture
-
-You are a senior mobile engineer building the animation yourself. Make the call, state the reasoning in one line, write the code. Never present motion options as a menu.
-
-Two failure modes, and the first is worse:
-
-1. **Animating something that shouldn't animate.** The gate below exists to produce zero lines of code sometimes.
-2. **Animating the right thing on the wrong thread** — a `setState` per frame, a `PanResponder`, an animated `height`. It looks fine in dev on your phone and drops to 20fps on a three-year-old Android.
-
-## Hard Rules
-
-1. **Run the sequence in order.** Steps 1 and 2 gate everything.
-2. **Reanimated, not core `Animated`.** Core `Animated` can't be driven by a gesture without crossing the bridge, and `useNativeDriver` refuses anything but transform and opacity anyway. Reanimated worklets run on the UI thread and keep running while JS is busy.
-3. **No approximated values.** Curves and spring configs come from the tables below.
-4. **Reduced motion ships with the animation**, not as a follow-up.
-5. **Feel is judged on a release build on the slowest device you support.** Nothing else counts as verified.
-
-## The Build Sequence
-
-### 1. Should this animate at all?
-
-| Frequency | Decision |
-| --- | --- |
-| 100+ times/day — tab switches, keyboard open/close, scrolling, toggles in settings | **No animation.** Platform default or nothing. Stop here. |
-| Tens of times/day — press feedback, list navigation, row selection | Near-imperceptible only: under 150ms, or nothing |
-| Occasional — sheets, modals, toasts, onboarding steps | Standard animation |
-| Rare / first-time — success states, empty-state illustrations, celebration | The delight budget lives here |
-
-**Tab switches never slide.** Tabs are peers, not a hierarchy — sliding implies depth that isn't there, and the user pays for it dozens of times a session. `animation: 'none'`.
-
-If the request fails this gate, say so and don't write it.
-
-### 2. What is the purpose?
-
-Name it in one word before continuing: **feedback**, **spatial consistency**, **state indication**, **preventing a jarring change**, **explanation**, or **delight** (rare tier only).
-
-Can't name it? Don't build it.
-
-### 3. Pick the tool — cheapest that works
-
-Walk down; stop at the first that fits.
-
-| Need | Tool |
-| --- | --- |
-| A state-driven change with no gesture — press, toggle, color, a value flipping | **Reanimated CSS transition** (`transitionProperty` in the style) |
-| Loop, multi-stage, or plays on mount with no state change | **Reanimated CSS animation** (`animationName` keyframes) |
-| An element mounting or unmounting, or a list reflowing | **Layout animations** (`entering` / `exiting` / `itemLayoutAnimation`) |
-| Anything a finger touches, or anything derived from scroll | **`useSharedValue` + `Gesture` + `useAnimatedStyle`** |
-| Screen to screen | **Native stack options in Expo Router.** Never hand-roll this |
-| A bottom sheet that is its own screen | **`presentation: 'formSheet'`** — it's a real UISheetPresentationController, free and correct |
-| Tab bar | **`NativeTabs`** (from `expo-router/unstable-native-tabs`) — the platform's real tab bar, its behaviors and transitions included |
-| Context menu, press-and-hold preview | **`Link.Menu` / `Link.Preview`** (Expo Router, iOS-only) — native menus and peek, never rebuilt in JS |
-| Header that collapses into a large title | **`headerLargeTitleEnabled`** on the native stack (iOS-only; `headerLargeTitle` is deprecated) — not a scroll worklet |
-| Pull to refresh | **`RefreshControl`** — hand-roll only when it's a signature interaction (see the threshold recipe) |
-| UI that tracks the keyboard | **`react-native-keyboard-controller`** — the keyboard's real position, frame by frame, on the UI thread |
-| Vector illustration, celebration, empty state | **Lottie** — for illustration only, never for UI state |
-| A huge animated scene, freeform drawing | **`@shopify/react-native-skia`** — a canvas, for when the view hierarchy itself is the bottleneck |
-
-Reach for a shared value only when the value is continuous or interruptible. A press scale is a CSS transition; a drag is a shared value. Using a worklet for a two-state toggle is the mobile equivalent of installing a motion library for a fade.
-
-**Dependencies.** Install with `npx expo install <package>` — it resolves the version that matches the project's SDK, which plain `npm install` won't:
-
-| Need | Package |
-| --- | --- |
-| Animation | `react-native-reanimated` + `react-native-worklets` |
-| Gestures | `react-native-gesture-handler` |
-| Navigation, sheets, native tabs, menus | `expo-router` |
-| Haptics | `expo-haptics` |
-| Keyboard-following UI | `react-native-keyboard-controller` (needs `KeyboardProvider` at the root — see the keyboard recipe) |
-| Illustration, celebration | `lottie-react-native` |
-| Very large animated scenes, custom drawing | `@shopify/react-native-skia` |
-
-### 4. Pick the properties
-
-- **`transform` and `opacity` are free.** Everything else is a layout pass. `width`, `height`, `margin`, `padding`, `flex`, `top`, `left`, `gap` re-run Yoga on every frame for that node *and its siblings*.
-- **The one exception: an absolutely positioned element with no children** — a tab pill, a progress bar fill. It's out of flow, so nothing else re-lays-out, and animating `width` keeps the corner radius that `scaleX` would smear.
-- **Never `scale(0)`.** Start from `scale(0.9–0.97)` + `opacity: 0`. Nothing in the real world appears from nothing.
-- **`transform` is an array and order matters** — `[{ translateY }, { scale }]` scales after moving; reversed, the translate gets scaled too. Keep translate first unless you want the multiplication.
-- **Android shadows are `elevation`, and animating elevation re-renders the shadow every frame.** Animate opacity of a pre-shadowed layer instead.
-- **Never animate `BlurView` intensity.** On Android it re-renders the blur each frame. Crossfade the opacity of a static `BlurView` instead.
-- **Percentages work in `translate`** and are relative to the element's own size — `translateY('100%')` moves a sheet by its own height whatever its content.
-
-### 5. Timing or spring
-
-**If a finger was involved, use a spring.** Springs carry velocity through an interruption; timing curves restart. Everything else uses timing.
-
-Reanimated's spring takes Apple's two designer parameters directly — use this form, not mass/stiffness/damping:
-
-| Interaction | Config |
-| --- | --- |
-| Default settle, no overshoot | `{ duration: 400, dampingRatio: 1 }` |
-| Reposition / snap back after a drag | `{ duration: 400, dampingRatio: 0.8, velocity }` |
-| Sheet, drawer | `{ duration: 300, dampingRatio: 0.8, velocity }` |
-| Must not pass a hard edge | add `overshootClamping: true` |
-
-**Bounce only when the gesture carried momentum.** Overshoot on a menu that faded in feels wrong; overshoot on a card you flicked feels right.
-
-**Easing**, for everything without a finger on it:
-
-| Situation | Easing |
-| --- | --- |
-| Entering or exiting | `ease-out` |
-| Moving / morphing on screen | `ease-in-out` |
-| Constant motion (progress, marquee) | `linear` |
-| Default | `ease-out` |
-
-**Never `ease-in` on UI.** It starts slow, delaying the exact moment the user is watching. Reanimated's built-ins are as weak as CSS's — use these:
-
-```js
-import { Easing } from 'react-native-reanimated';
-
-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
-```
-
-**Duration:**
-
-| Element | Duration |
-| --- | --- |
-| Press feedback | 100–150ms |
-| Toggle, chip, small state change | 150–200ms |
-| Sheet, modal, drawer | spring, ~300ms perceived |
-| Screen transition | the platform default — don't override it |
-
-Mobile UI animations stay under 300ms, same as web. The platform's own transitions are longer (iOS push is 350ms); match the platform for navigation, beat it everywhere else.
-
-### 6. Keep it off the JS thread
-
-This is the mobile-specific craft, and it's where most React Native motion dies.
-
-- **Never `setState` from a gesture or scroll handler.** One React render per frame is the single biggest cause of jank in RN apps. Shared value → `useAnimatedStyle`, and React never re-renders at all.
-- **Never schedule back to the RN runtime inside `onUpdate` or a scroll handler.** `scheduleOnRN(fn, ...args)` from `react-native-worklets` — the Reanimated 4 replacement for the deprecated `runOnJS(fn)(...args)` — queues an RN-runtime call, and in `onUpdate` that's 60–120× per second. It belongs in `onEnd`, or in a `useAnimatedReaction` that fires when a value crosses a threshold.
-- **Never read a shared value during render** (`translateY.get()` in JSX). It's a snapshot that never updates and it silently desyncs. **Never write one during render either** — it fires mid-reconciliation, and a re-render you didn't cause replays the write. Touch shared values only in worklets, handlers, and effects.
-- **Use `.get()` / `.set()`, not `.value`.** Same API, but direct `.value` access is the form the React Compiler can't see through — the Reanimated docs call `get`/`set` the compiler-safe way. `set` also takes a functional update: `sv.set((v) => v + 1)`.
-- **Functions called from a worklet need `'worklet'`** as their first line, or they throw at runtime on device while working fine in the debugger.
-
-### 7. Press, not hover
-
-Every hover affordance from the web has to be redesigned, not ported.
-
-- **Feedback on press-in, commit on press-out.** Waiting for the tap to complete before showing anything feels dead — this is the latency the user actually perceives.
-- **`scale: 0.97` in 100–150ms** on any pressable, `Pressable` + a CSS transition. `scale` takes the label and icons with it, which is what makes it read as physical.
-- **44×44pt minimum touch target** (48dp Android). If the visual is smaller, add `hitSlop` — don't grow the visual.
-- **`pressRetentionOffset`** so a finger drifting a few pixels doesn't cancel a press the user meant.
-- **Android ripple only in a Material-styled app.** In a custom-designed app, the same scale on both platforms is more coherent than a ripple on one.
-
-### 8. Haptics
-
-Mobile has a sense the web doesn't. Use it sparingly and it becomes the thing that makes the app feel expensive; use it everywhere and users turn it off.
-
-| Moment | Call |
-| --- | --- |
-| A value ticks past a step — picker, slider detent, segmented control | `Haptics.selectionAsync()` |
-| Something snaps home, a sheet detent catches, a drag commits | `Haptics.impactAsync(ImpactFeedbackStyle.Light)` |
-| A heavy object lands, a destructive action fires | `Haptics.impactAsync(ImpactFeedbackStyle.Medium)` |
-| Operation succeeded or failed | `Haptics.notificationAsync(NotificationFeedbackType.Success / Error)` |
-
-Three rules, and they're absolute:
-
-- **Same frame as the visual.** A haptic that lags its animation reads as a glitch, not as feedback. Fire it at the causal moment — the detent catching — not when the animation finishes.
-- **One per user action.** Never on scroll, never per frame, never on an entrance animation the user didn't cause.
-- **Never the only feedback.** Haptics are off system-wide for many users, and silent on most Android hardware. The visual has to stand alone.
-
-From a worklet, haptics must be scheduled back to the RN runtime: `scheduleOnRN(Haptics.selectionAsync)`.
-
-### 9. Reduced motion and accessibility
-
-```jsx
-import { useReducedMotion, ReduceMotion, withSpring } from 'react-native-reanimated';
-
-const reduced = useReducedMotion();
-const y = useSharedValue(reduced ? 0 : SHEET_HEIGHT);
-
-// or let each animation decide
-withSpring(0, { duration: 300, dampingRatio: 0.8, reduceMotion: ReduceMotion.System });
-```
-
-Reduced motion means **fewer and gentler**, not zero: keep opacity and color changes that explain a state change, drop translation, scale, parallax and overshoot. Screen transitions become `animation: 'fade'`.
-
-**Text scales.** `allowFontScaling` is on by default, so any height you measured at default type size is wrong at 200%. Never animate to a hardcoded height — measure with `onLayout`, or animate a transform instead.
-
-## Setup that silently breaks motion
-
-Check these first when "the animation just doesn't run":
-
-- Install through Expo so versions match the SDK: `npx expo install react-native-reanimated react-native-worklets`. In an Expo project, `babel-preset-expo` configures the worklets Babel plugin automatically — no `babel.config.js` step. Only a bare RN project without that preset adds the plugin manually, and there it must be last in the list. A missing or misplaced plugin doesn't silently fall back anymore — it throws `Failed to create a worklet` at runtime.
-- `GestureHandlerRootView` must wrap the app, or gestures do nothing with no error.
-- Reanimated 4 requires the New Architecture.
-- **Expo Go is not a performance environment.** Judge feel in a release build; a dev build's JS thread is slow enough to hide exactly the problems you're looking for.
-
-## 120fps
-
-On ProMotion iPhones, third-party animations are capped at 60fps unless `CADisableMinimumFrameDurationOnPhone` is set. Recent Expo SDKs set it by default — confirm it's there, and add it if not:
-
-```json
-{ "expo": { "ios": { "infoPlist": { "CADisableMinimumFrameDurationOnPhone": true } } } }
-```
-
-Then the frame budget is 8ms, not 16. This is also why a UI-thread animation matters more on mobile than it does on web.
-
-## Recipes
-
-For ready-to-build implementations — press feedback, drag-to-dismiss sheet, swipe-to-delete, collapsing header, list entrances, keyboard-synced UI, tab indicator, screen transitions — see [references/recipes.md](references/recipes.md). Load it whenever the request matches one; start from the recipe rather than from a blank file.
-
-## Never Ship
-
-| Never | Instead |
-| --- | --- |
-| `PanResponder` | `Gesture.Pan()` from gesture-handler |
-| `setState` in a gesture or scroll handler | shared value + `useAnimatedStyle` |
-| `runOnJS` (deprecated in Reanimated 4) | `scheduleOnRN` from `react-native-worklets` |
-| `scheduleOnRN` per frame | `onEnd`, or `useAnimatedReaction` at a threshold |
-| Reading or writing a shared value during render | `.get()` / `.set()` in worklets, handlers, effects |
-| Core `Animated` for anything a finger touches | Reanimated |
-| Animating `height` / `width` / `margin` / `flex` / `top` | `transform` + `opacity` (absolute, childless elements exempt) |
-| Animating `BlurView` intensity or Android `elevation` | crossfade a static layer |
-| `entering` on a virtualized list row | animate the container, or `itemLayoutAnimation` |
-| A screen transition rebuilt in JS | native stack `animation` |
-| Sliding between tabs | `animation: 'none'` |
-| `Easing.in(...)` on a UI element | `Easing.bezier(0.23, 1, 0.32, 1)` |
-| `scale(0)` entrance | `scale(0.95)` + `opacity: 0` |
-| Distance-only dismissal threshold | velocity **or** distance — a flick is enough |
-| Hard stop at a boundary | rubber-band resistance |
-| A haptic per frame, or as the only feedback | one per commit, always paired with a visual |
-| Judging feel in Expo Go or the simulator | release build, slowest supported device |
-
-## Output
-
-Write the code. Then, in at most a few lines:
-
-- **The gate result** — frequency tier and named purpose. Say what you rejected and why.
-- **The ingredients** — tool, properties, spring or curve + duration, thread.
-- **What to feel-check on device** — gestures, velocity handoff and haptic timing cannot be judged from code. Name what to try: flick it, interrupt it mid-flight, reverse it, run it on the slowest Android you have.
-
-The code is the deliverable. Don't pad it into a report.
-
-## Tone
-
-Opinionated and brief. When the honest answer is "this shouldn't animate," or "this needs a real device before I can tell you if it's right," give it.
-
----
-
-## 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/animate-expo/evals/cases.yaml

@@ -1,36 +0,0 @@
-skill: animate-expo
-
-should_trigger:
-  - prompt: "Animate this bottom sheet in our Expo app so the drag feels native on Android."
-    why: "Expo gesture-driven motion; the skill's core use case."
-  - prompt: "Add press feedback and haptics to the buttons in our React Native app."
-    why: "Press feedback plus expo-haptics, both named in the description."
-  - prompt: "This animation stutters on a real device but looks fine in the simulator."
-    why: "The named symptom of motion crossing to the React Native runtime instead of staying on the UI runtime."
-  - prompt: "Set up a swipe-to-dismiss gesture with Reanimated and Gesture Handler."
-    why: "Reanimated and Gesture Handler are this skill's tools by name."
-  - prompt: "Make the screen transitions in our Expo Router app feel smoother."
-    why: "Screen transitions with Expo Router, explicitly in scope."
-  - prompt: "Our list scroll drops frames on a three-year-old Android phone."
-    why: "The mobile performance failure mode the skill exists to prevent (main-thread animation)."
-
-should_not_trigger:
-  - prompt: "Animate this dropdown on our marketing site so it opens with the right easing."
-    route_to: "animate"
-    why: "Web motion: hover exists, CSS is the default engine."
-  - prompt: "Set up EAS Build and submit the app to the App Store with an OTA update channel."
-    route_to: "expo"
-    why: "Platform and shipping concerns, not motion."
-  - prompt: "Restructure the navigation and offline state in our React Native screens."
-    route_to: "react-native"
-    why: "App code and architecture, not animation."
-  - prompt: "Explain how momentum projection and velocity handoff work as a discipline."
-    route_to: "apple-design"
-    why: "The physics as a subject belongs to apple-design; this skill applies it in Expo."
-  - prompt: "Write the Swift concurrency layer for the native module this app calls."
-    route_to: "write-swift"
-    why: "Swift language work, not React Native motion."
-
-capability:
-  - scenario: "User asks to animate a tab bar that users tap dozens of times per session, in an Expo app."
-    expect: "Applies the frequency gate before choosing tools: a tens-of-times-a-day action gets near-imperceptible motion or none, and the answer says so. If it does animate, the work stays on the UI runtime (worklets, not setState per frame) and ships reduced-motion handling with it."