animations-native
Authors performant React Native / Expo animations and gestures with Reanimated and react-native-gesture-handler on the UI thread; web animations go to `animations`. Triggers on "reanimated", "react native animation", "gesture handler", "swipe gesture", "/animations-native".
mthines · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mthines/agent-skills --skill animations-native技能说明
name: animations-native
description: >
Authors performant React Native / Expo animations and gestures with Reanimated
and react-native-gesture-handler on the UI thread; web animations go to
animations. Triggers on "reanimated", "react native animation", "gesture
handler", "swipe gesture", "/animations-native".
argument-hint: '[brainstorm]'
license: MIT
metadata:
author: mthines
version: '1.0.0'
workflow_type: applied
tags:
- react-native
- expo
- reanimated
- react-native-gesture-handler
- animations
- gestures
- worklets
- performance
- accessibility
- reduced-motion
- moti
- lottie
- rive
- haptics
Animations (React Native / Expo)
Produces or reviews React Native animations that hold 60/120 fps by running motion on the UI thread via Reanimated worklets, respect the OS Reduce Motion setting, and use the cheapest tool for the job — the Reanimated CSS API first, the worklet/hooks API for interactive motion, gesture-handler for touch, and asset runtimes (Lottie / Rive) only for designer-authored art.
This
SKILL.mdis a thin index. Detailed rules live inrules/*.mdand load on demand. This is the native sibling of theanimationsskill — that one owns web (CSS, Motion, View Transitions); this one owns React Native / Expo.
Core Bet
Animate transform and opacity, and drive the value from the UI thread.
Those are the properties the New Architecture applies to a mounted view without a Yoga layout recalculation — the RN analog of the web "composite-only" rule.
Layout props (width, height, top, left, flex, margin) recompute layout every frame and jank.
Driving the value from the UI thread (a Reanimated shared value, not React useState) keeps motion smooth even when the JS thread is busy.
Full property table and the threading model in rules/reanimated-core.md.
Brainstorm Mode — interaction → feedback
When the question is what the motion should be (not how to build it), the reasoning is platform-agnostic and already lives in the animations skill.
Read the five-question brainstorm and the verb→motion catalog in ../animations/rules/interaction-feedback.md — verb, reversibility, initiator, spatial source, affordance load, plus the intensity ladder and direction principle.
The duration bands and easing conventions carry straight over to native; the native-specific spring/personality notes are in rules/reanimated-core.md.
Then hand off to the decision flow below for the mechanics.
Decision flow
Walk in order. First match wins.
| # | Signal | Tool |
|---|---|---|
| 1 | State-controlled, self-contained motion (pulse, entrance, a value tied to React state) | Reanimated CSS API (animationName / transitionProperty) (reanimated-core.md) |
| 2 | Enter / exit / reorder of a component or list item | Reanimated layout animations (entering / exiting / layout) (reanimated-core.md) |
| 3 | Gesture-driven, scroll-driven, or interruptible motion | Reanimated worklet/hooks API + gesture-handler (gestures.md) |
| 4 | Simple isolated fade with no dependency budget | RN core Animated + useNativeDriver: true (libraries.md) |
| 5 | Framer-Motion-style declarative props on a Reanimated 3 stack | Moti (check Reanimated-4 compatibility) (libraries.md) |
| 6 | Designer-authored After Effects asset, fixed timeline | Lottie (libraries.md) |
| 7 | Designer-authored interactive asset (state machine, inputs) | Rive (libraries.md) |
If two rows match, pick the lower-numbered one — it has fewer dependencies.
Workflow
For any RN animation task — author or review — walk these phases.
| Phase | Name | Rule file | Gate |
|---|---|---|---|
| A | Brainstorm feedback (entry is "what?") | ../animations/rules/interaction-feedback.md | If the user describes an interaction (a verb), the five questions are answered and a catalog row picked before mechanics. Skip if they describe a primitive ("fade this in"). |
| 0 | Choose the property & thread | rules/reanimated-core.md | Animated property is transform / opacity (or backgroundColor); the value is a shared value on the UI thread, not React state. |
| 1 | Pick the API | rules/reanimated-core.md, rules/libraries.md | Decision flow above is followed; CSS API / layout animation preferred over hand-rolled worklets when it fits. |
| 2 | Wire gestures (if interactive) | rules/gestures.md | GestureHandlerRootView present; callbacks drive shared values; state setters go through scheduleOnRN / runOnJS; ScrollView coexistence handled. |
| 3 | Time it | rules/reanimated-core.md | Duration 100–500 ms; ease-out entrances, ease-in exits; springs for gesture-driven / interruptible motion. |
| 4 | Respect Reduce Motion | rules/accessibility.md | Reanimated respects the OS setting by default; library assets (Lottie/Rive) and non-Reanimated motion are gated; motion is reduced, not removed. |
| 5 | Add haptics (high-stakes only) | rules/accessibility.md | Haptic fires at the visual state change, paired with a visual cue, never haptic-only. |
| 6 | Measure | rules/performance.md | Perf Monitor shows the animation holding on the UI thread; UI-thread and JS-th |