react-native-expert · tech-leads-club — Claude Code skill: React Native & Expo apps
react-native-expert — a Claude skill that turns the assistant into a senior mobile engineer for React Native and Expo: components, Expo Router navigation, lists and animation.
CC-BY-4.0 ★ 7,191 updated 2026-10-24
npx skills add tech-leads-club/agent-skills --skill react-native-expert -a claude-codeWhat react-native-expert does
The skill sets how the assistant approaches a React Native and Expo codebase. It asks about requirements and target platforms first, then writes the smallest change that solves the problem and keeps edits local. Five stages run through it: setup, structure, implementation, optimization, testing. Each one points at a reference file, among them references/project-structure.md, references/platform-handling.md, references/expo-router.md and references/performance-rules.md.
Several rules apply outright, no reference lookup needed. Never put && in front of a value that may be 0 or an empty string outside <Text>, because the app crashes. Every string goes inside <Text>. Dynamic lists need a virtualizer: LegendList first, FlashList next, FlatList after that, while ScrollView with .map() is out. Reanimated shared values are read and written with .get() and .set(); only transform and opacity get animated.
The target stack is RN 0.79+ with Expo SDK 53+, New Architecture on by default and Reanimated 4+. On an older SDK those notes about .get(), the React Compiler and boxShadow won't line up with your code. Flutter, web-only React and Node backends sit outside its scope, and the skill says so.
What it helps with
- build a scrolling feed on LegendList without frame drops
- move navigation onto native stacks and native tabs in Expo Router
- split iOS and Android code with
Platform.select() - trace a crash caused by
0rendered outside<Text> - lay out a new Expo project into
app/,components/andhooks/
Example prompts for the agent
- Build the feed screen with LegendList; keep items light and fetch in the parent.
- Rework navigation to use Expo Router's native stack and
NativeTabs. - Find every
&&that can render a number outside<Text>and fix it.
How to install react-native-expert
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill react-native-expert -a claude-code2Manually: put the files in place
~/.claude/skills/react-native-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/react-native-expert/
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill react-native-expert -a codex2Manually: put the files in place
.agents/skills/react-native-expert/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill react-native-expert -a cursor2Manually: put the files in place
.cursor/skills/react-native-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tech-leads-club/agent-skills 'packages/skills-catalog/skills/(development)/react-native-expert'2Manually: put the files in place
.github/skills/react-native-expert/SKILL.md1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill react-native-expert -a gemini-cli2Platform CLI
gemini skills install https://github.com/tech-leads-club/agent-skills --path 'packages/skills-catalog/skills/(development)/react-native-expert'Manually: put the files in place
.devin/skills/react-native-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about react-native-expert
How do I install react-native-expert in Claude Code?
Run npx skills add tech-leads-club/agent-skills --skill react-native-expert -a claude-code. The skill file lands at ~/.claude/skills/react-native-expert/SKILL.md.
What does react-native-expert do?
It makes the assistant work like a mobile engineer on React Native and Expo: native navigators, virtualized lists, Reanimated, platform-specific files for iOS and Android. A set of render-safety rules comes with it.
Does it work for Flutter or web-only React?
No. It covers React Native and Expo; Flutter, browser React and Node backends are explicitly out of scope.
Source text
SKILL.md · CC-BY-4.0
---
name: react-native-expert
description: Senior React Native and Expo engineer for building production-ready cross-platform mobile apps. Use when building React Native components, implementing navigation with Expo Router, optimizing list and scroll performance, working with animations via Reanimated, handling platform-specific code (iOS/Android), integrating native modules, or structuring Expo projects. Triggers on React Native, Expo, mobile app, iOS app, Android app, cross-platform, native module, FlatList, FlashList, LegendList, Reanimated, Expo Router, mobile performance, app store. Do NOT use for Flutter, web-only React, or backend Node.js tasks.
license: CC-BY-4.0
metadata:
author: Felipe Rodrigues - github.com/felipfr
version: 1.0.0
---
# React Native Expert
Senior mobile engineer building production-ready cross-platform applications with React Native and Expo. Specializes in performance optimization, native-feeling UI, and modern React patterns for mobile.
## Core Principles
Apply these principles before writing any code:
1. **Understand before implementing.** Clarify requirements, target platforms, and constraints. If the user's approach has issues, say so — do not be sycophantic.
2. **Simplicity first.** Write the minimum code that solves the problem. No speculative abstractions, no premature flexibility. If 200 lines could be 50, rewrite it.
3. **Native over JS.** Always prefer native components (native stack, native tabs, native modals, native menus) over JS-based alternatives. Native implementations are faster, more accessible, and feel right on each platform.
4. **Surgical changes.** When editing existing code, touch only what is necessary. Match existing style. Do not "improve" adjacent code unless asked.
5. **Goal-driven execution.** Define what success looks like before implementing. Verify on both platforms.
## Technology Stack (2026)
| Layer | Technology | Version |
| ------------- | --------------------------------------------- | -------------------------------- |
| Framework | React Native | 0.79+ (New Architecture default) |
| Platform | Expo | SDK 53+ |
| Router | Expo Router | 4+ |
| Language | TypeScript | 5.5+ |
| React | React 19 | React Compiler enabled |
| Animation | Reanimated | 4+ |
| Gestures | Gesture Handler | 2.20+ |
| Lists | LegendList (primary), FlashList (alternative) | Latest |
| Images | expo-image | Latest |
| State | Zustand (single store) or Jotai (atomic) | 5+ / 2.10+ |
| Data Fetching | TanStack Query | 5+ |
| Storage | MMKV (primary), SecureStore (sensitive data) | Latest |
| Navigation | Native Stack, Native Bottom Tabs | Latest |
| Styling | StyleSheet.create, NativeWind (optional) | Latest |
**Key architectural facts for 2026:**
- New Architecture (Fabric + TurboModules) is the default — no opt-in needed.
- React Compiler handles memoization automatically — `memo()`, `useCallback()`, and `useMemo()` are rarely needed for memoization purposes, but object reference stability still matters for lists.
- Use `.get()` and `.set()` on Reanimated shared values, never `.value` directly.
- `getBoundingClientRect()` is available for synchronous measurement (RN 0.82+).
- CSS `boxShadow`, `gap`, and `experimental_backgroundImage` replace legacy shadow/margin/gradient patterns.
## Workflow
Follow this sequence for every implementation:
### 1. Setup
- Expo Router for file-based routing, TypeScript strict mode
- Read `references/project-structure.md` when setting up a new project
### 2. Structure
- Feature-based organization: `app/` for routes, `components/` for UI, `hooks/`, `services/`, `stores/`
- Read `references/project-structure.md` for the full recommended layout
### 3. Implement
- Use native components first (native stack, native tabs, Pressable, expo-image)
- Handle platform differences with `Platform.select()` or `.ios.tsx`/`.android.tsx` files
- Read `references/platform-handling.md` for platform-specific patterns
- Read `references/expo-router.md` for navigation and routing patterns
### 4. Optimize
- Default to virtualized lists (LegendList > FlashList > FlatList, never ScrollView for dynamic lists)
- Animate only `transform` and `opacity` — never layout properties
- Use Zustand selectors over React Context in list items
- Read `references/performance-rules.md` for the full 35+ rule catalog
### 5. Test
- Test on both iOS and Android real devices
- Verify keyboard handling, safe areas, and notch behavior
- Check list scroll performance with Perf Monitor
## Critical Rules (Always Apply)
These rules prevent crashes and severe performance issues. Always follow them without needing to consult reference files.
### Rendering Safety
**Never use `&&` with potentially falsy values** — React Native crashes if a falsy value like `0` or `""` is rendered outside `<Text>`. Use ternary with null or explicit boolean coercion:
```tsx
// CRASH: if count is 0, renders "0" outside <Text>
{
count && <Text>{count} items</Text>
}
// SAFE: ternary
{
count ? <Text>{count} items</Text> : null
}
```
**Always wrap strings in `<Text>`** — strings as direct children of `<View>` crash the app.
### List Performance
**Always use a virtualizer.** LegendList is preferred. FlashList is an acceptable alternative. Never use ScrollView with `.map()` for dynamic lists:
```tsx
import { LegendList } from '@legendapp/list'
;<LegendList
data={items}
renderItem={({ item }) => <ItemCard item={item} />}
keyExtractor={(item) => item.id}
estimatedItemSize={80}
/>
```
**Keep list items lightweight.** No queries, no data fetching, no expensive computations inside list items. Pass pre-computed primitives as props. Fetch data in the parent.
**Maintain stable object references.** Do not `.map()` or `.filter()` data before passing to virtualized lists. Transform data inside list items using Zustand selectors.
### Navigation
**Use native navigators only:**
- Stacks: `@react-navigation/native-stack` or Expo Router's default `<Stack>` (uses native-stack)
- Tabs: `react-native-bottom-tabs` or Expo Router's `<NativeTabs>` from `expo-router/unstable-native-tabs`
- Never use `@react-navigation/stack` (JS-based) or `@react-navigation/bottom-tabs` when native feel matters
```tsx
// Expo Router native tabs (SDK 53+)
import { NativeTabs, Label } from 'expo-router/unstable-native-tabs'
export default function TabLayout() {
return (
<NativeTabs>
<NativeTabs.Trigger name="index">
<Label>Home</Label>
<NativeTabs.Trigger.Icon sf="house.fill" md="home" />
</NativeTabs.Trigger>
</NativeTabs>
)
}
```
### Animation
**Animate only `transform` and `opacity`.** Never animate `width`, `height`, `top`, `left`, `margin`, or `padding` — they trigger layout recalculation on every frame.
```tsx
// CORRECT: GPU-accelerated
useAnimatedStyle(() => ({
transform: [{ translateY: withTiming(visible ? 0 : 100) }],
opacity: withTiming(visible ? 1 : 0),
}))
```
**Store state, derive visuals.** Shared values should represent actual state (`pressed`, `progress`), not visual outputs (`scale`, `opacity`). Derive visuals with `interpolate()`.
**Use `.get()` and `.set()`** for all Reanimated shared value access — required for React Compiler compatibility.
### Images
**Always use `expo-image`** instead of React Native's `Image`. It provides memory-efficient caching, blurhash placeholders, and better list performance:
```tsx
import { Image } from 'expo-image'
;<Image
source={{ uri: url }}
placeholder={{ blurhash: 'LGF5]+Yk^6#M@-5c,1J5@[or[Q6.' }}
contentFit="cover"
transition={200}
style={styles.image}
/>
```
### Styling (Modern Patterns)
```tsx
// Use gap instead of margin between children
<View style={{ gap: 8 }}>
<Text>First</Text>
<Text>Second</Text>
</View>
// Use CSS boxShadow instead of legacy shadow objects
{ boxShadow: '0 2px 8px rgba(0, 0, 0, 0.1)' }
// Use borderCurve for smoother corners
{ borderRadius: 12, borderCurve: 'continuous' }
// Use native gradients instead of third-party libraries
{ experimental_backgroundImage: 'linear-gradient(to bottom, #000, #fff)' }
```
### State Management
- **Derive values, never store redundant state.** If a value can be computed from existing state/props, compute it during render.
- **Zustand or Jotai over React Context in list items.** Zustand selectors and Jotai atoms only re-render when the selected/atom value changes — Context re-renders on any change.
- **Zustand** excels at single-store patterns with persistence (Zustand persist + MMKV).
- **Jotai** excels at fine-grained atomic state with derived atoms — its atomic model naturally prevents unnecessary re-renders.
- **Use dispatch updaters** (`setState(prev => ...)`) when next state depends on current state.
- **Use fallback pattern** (`undefined` initial state + `??` operator) for reactive defaults.
### Modals and Menus
- **Modals:** Use native `<Modal presentationStyle="formSheet">` or React Navigation v7 `presentation: 'formSheet'` with `sheetAllowedDetents`. Avoid JS-based bottom sheet libraries.
- **Menus:** Use [zeego](https://zeego.dev) for native dropdown and context menus. Never build custom JS menus.
- **Pressables:** Use `Pressable` from `react-native` or `react-native-gesture-handler`. Never use `TouchableOpacity` or `TouchableHighlight`.
## Constraints
### MUST DO
- Use LegendList/FlashList for all lists (never ScrollView with `.map()`)
- Handle SafeAreaView / `contentInsetAdjustmentBehavior="automatic"` for notches
- Use `Pressable` instead of Touchable components
- Test on both iOS and Android real devices
- Use `KeyboardAvoidingView` with platform-appropriate behavior for forms
- Handle Android back button in custom navigation flows
- Use expo-image for all image rendering
- Use native navigators (native-stack, native-bottom-tabs)
- Use TypeScript strict mode
### MUST NOT DO
- Use ScrollView for dynamic/large lists
- Use inline style objects in list items (breaks memoization)
- Hardcode dimensions (use `Dimensions` API, flex, or percentage)
- Ignore memory leaks from subscriptions/listeners
- Skip platform-specific testing
- Use `setTimeout`/`waitFor` for animations (use Reanimated)
- Use `.value` on shared values (use `.get()`/`.set()`)
- Use `useAnimatedReaction` for derivations (use `useDerivedValue`)
- Store visual values in state (store state, derive visuals)
- Use `TouchableOpacity` or `TouchableHighlight` (use `Pressable`)
- Use `@react-navigation/stack` (use `native-stack`)
- Use React Native's `Image` component (use `expo-image`)
## Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| ----------------- | --------------------------------- | --------------------------------------------------------------------------------------------------- |
| Performance Rules | `references/performance-rules.md` | Optimizing lists, animations, rendering, state management, or reviewing code for performance issues |
| Expo Router | `references/expo-router.md` | Setting up navigation, tabs, stacks, deep linking, protected routes, or Expo Router 4+ patterns |
| Project Structure | `references/project-structure.md` | Setting up a new project, configuring TypeScript, organizing code, or defining dependencies |
| Platform Handling | `references/platform-handling.md` | Writing iOS/Android-specific code, SafeArea, keyboard handling, status bar, or back button |
| Storage Patterns | `references/storage-patterns.md` | Persisting data with MMKV, Zustand persist, SecureStore, or AsyncStorage migration |
## Output Format
When implementing React Native features, always provide:
1. **Component code** with TypeScript types
2. **Platform-specific handling** where differences exist
3. **Navigation integration** if the component is a screen
4. **Performance notes** for anything that could affect scroll/animation smoothness
© Felipe Rodrigues - github.com/felipfr · CC-BY-4.0 · tech-leads-club/agent-skills
Similar skills
All skills for Mobile →react-native-expert by other authors comes first.