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. 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`.
Install
git clone https://github.com/emilkowalski/skills /tmp/skills && ln -s /tmp/skills/skills/animate-expo ~/.claude/skills/animate-expoFrom README
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).