vercel-react-native-skills

Use a virtualized list like LegendList or FlashList instead of ScrollView, pass stable object references as data, and give list items primitive props so memo() shallow comparison works. Avoid inline objects and callbacks inside renderItem since new references break memoization.

Using {value && <Component />} crashes when value is an empty string or 0, because React Native tries to render the falsy value as text outside a Text component. Use a ternary with null, explicit boolean coercion, or an early return instead.

Both are virtualized lists that render only visible items, reducing memory and mount time compared to ScrollView. The rules cover both, including getItemType for heterogeneous lists and estimatedItemSize for accurate recycling.

Yes, but you must use .get() and .set() instead of reading or writing .value directly on shared values, since the compiler cannot track property access. Destructuring functions early in render also keeps references stable for compiler memoization.

Always prefer transform and opacity because they run on the GPU without triggering layout recalculation. Animating width, height, margin, or padding forces layout on every frame and causes jank.

Native dependencies must be listed in the app package's package.json, not only in shared packages, because autolinking only scans the app's node_modules. Use exact single versions across the monorepo to avoid duplicate bundles.