animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right ā should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades.
Install / Use
npx skills add emilkowalski/skills --skill animate-expoInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of animate-expo
animate-expo scores 98/100 on our quality scale, 102nd of 4,698 Development & Engineering skills we index (top 3%).
Its SKILL.md is 17 KB long, well organised into 20 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 40,844 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so animate-expo is actively maintained.
- Our last check on 2026-11-14 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit ā read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk ā read a skill before letting an agent act on it.
animate-expo compared with similar skills
All 4 of these similar skills score higher than animate-expo; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| animate-expo (this skill)by emilkowalski | 98 | 40.8k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install animate-expo?
- Run
npx skills add emilkowalski/skills --skill animate-expo. The install tabs above show the steps for each supported agent. - Which AI agents does animate-expo work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is animate-expo safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is animate-expo still maintained?
- The repository was last updated about 2 months ago, so animate-expo is actively maintained.
Skill content
View source on GitHubname: animate-expo
description: Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right ā should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.
Building Animations in Expo
Initial Response
When this skill is first invoked without a specific question, respond only with:
I'm ready to build animations in Expo and React Native that feel right on a real device, my knowledge comes from Emil Kowalski's animation philosophy.
Do not provide any other information until the user asks a question.
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:
- There is no hover. Every affordance the web puts in hover has to live in press, position, or nothing.
- 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.
- 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:
- Animating something that shouldn't animate. The gate below exists to produce zero lines of code sometimes.
- Animating the right thing on the wrong thread ā a
setStateper frame, aPanResponder, an animatedheight. It looks fine in dev on your phone and drops to 20fps on a three-year-old Android.
Hard Rules
- Run the sequence in order. Steps 1 and 2 gate everything.
- Reanimated, not core
Animated. CoreAnimatedcan't be driven by a gesture without crossing the bridge, anduseNativeDriverrefuses anything but transform and opacity anyway. Reanimated worklets run on the UI thread and keep running while JS is busy. - No approximated values. Curves and spring configs come from the tables below.
- Reduced motion ships with the animation, not as a follow-up.
- 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
transformandopacityare free. Everything else is a layout pass.width,height,margin,padding,flex,top,left,gapre-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
widthkeeps the corner radius thatscaleXwould smear. - Never
scale(0). Start fromscale(0.9ā0.97)+opacity: 0. Nothing in the real world appears from nothing. transformis 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
BlurViewintensity. On Android it re-renders the blur each frame. Crossfade the opacity of a staticBlurViewinstead. - Percentages work in
translateand 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:
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
setStatefrom 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
onUpdateor a scroll handler.scheduleOnRN(fn, ...args)fromreact-native-workletsā the Reanimated 4 replacement for the deprecatedrunOnJS(fn)(...args)ā queues an RN-runtime call, and inonUpdatethat's 60ā120Ć per second. It belongs inonEnd, or in auseAnimatedReactionthat 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.valueaccess is the form the React Compiler can't see through ā the Reanimated docs callget/setthe compiler-safe way.setalso 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.97in 100ā150ms on any pressable,Pressable+ a CSS transition.scaletakes 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. pressRetentionOffsetso a finger drifting a few pixels doesn't cancel a press the user meant.- **Android ripple on
Truncated for display ā read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code ā from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k𤯠LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit ā see the Safety scan above for what the skill file itself contains.
