vercel-react-native-skills

Use a list virtualizer like LegendList or FlashList instead of ScrollView, pass primitive props to memoized list items, hoist callbacks to the list root, and keep item components lightweight without queries or heavy hooks. Stable object references in the data array prevent full re-renders.

This crash happens when a string or falsy value like 0 or an empty string is rendered as a direct child of a View. Wrap all strings in Text components and replace {value && <Component />} with ternaries or explicit boolean coercion.

Use useDerivedValue when computing one shared value from another, since it is declarative and tracks dependencies automatically. Reserve useAnimatedReaction for side effects that produce no value, such as triggering haptics or calling runOnJS.

Yes, several rules address React Compiler compatibility, including destructuring functions early in render and using .get()/.set() instead of .value on Reanimated shared values. With the compiler enabled, manual memo() and useCallback() optimizations become less critical.

Use native navigators such as @react-navigation/native-stack or expo-router's default stack, which run transitions on platform APIs like UINavigationController. JS-based navigators lack native performance, large titles, and automatic safe area handling.

Autolinking only scans the native app's node_modules, so packages with native code like react-native-reanimated must be listed in the app package's dependencies even if a shared package also uses them. Keep single exact versions across the monorepo to avoid duplicate bundles.