Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill provides a structured approach to mobile motion, guiding developers through the sequence of decisions that determine how an animation feels. It focuses on thread management, property selection, and the hand-off between gestures and motion to ensure interfaces remain responsive.
Designed for Expo developers, the guidance covers practical implementation using Reanimated, Gesture Handler, and expo-haptics to build screen transitions, sheets, and tactile press feedback.
WHO IT'S FOR
React Native / Expo developers
implementing high-performance mobile animations and gestures
Frontend engineers
optimizing web animation frame rates and performance
Product designers
defining motion logic and animation behavior
UI/UX engineers
building polished transitions and interactive components
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Use pick-ui-library to recommend a library for toast notifications in this frontend project. Check package.json first, recommend one library from the curated list, and briefly explain the choice. If an existing dependency already covers this, flag the recommendation without changing dependencies.
A component diff containing animation or transition code.
Brief context about how often users encounter the interaction and whether it is keyboard initiated.
Use review-animations to review the supplied component diff. Focus on whether its motion is justified, easing and duration, transform origin, interruptibility, animated properties, and reduced-motion support. Report concrete findings without implementing changes.
The target component and its existing props, fixture, mock, or API stub.
Available validation schemas or API contracts defining field limits.
A development environment or prototype route for the data toggle.
Use break-ui to stress-test the supplied component with plausible worst-case data. Inspect the values it renders and any available schema limits, then provide demo and worst-case datasets behind a dev-only toggle through its existing data boundary. Report what breaks and propose a fix for each issue, then stop before fixing.