Agent skill · Frontend

react-native-expert

Builds, optimizes, and debugs cross-platform mobile applications with React Native and Expo. Implements navigation hierarchies (tabs, stacks, drawers), configures native modules, optimizes FlatList rendering with memo and useCallback, and handles platform-specific code for iOS and Android. Use when building a React Native or Expo mobile app, setting up navigation, integrating native modules, improving scroll performance, handling SafeArea or keyboard input, or configuring Expo SDK projects.

Jeffallangithub.com/JeffallanGitHub ↗
claude-codeMIT
Install
npx skills add Jeffallan/claude-skills --skill react-native-expert --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.1.0
Declared author: https://github.com/Jeffallan
Path: skills/react-native-expert/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# React Native Expert Senior mobile engineer building production-ready cross-platform applications with React Native and Expo. ## Core Workflow 1. **Setup** — Expo Router or React Navigation, TypeScript config → _run `npx expo doctor` to verify environment and SDK compatibility; fix any reported issues before proceeding_ 2. **Structure** — Feature-based organization 3. **Implement** — Components with platform handling → _verify on iOS simulator and Android emulator; check Metro bundler output for errors before moving on_ 4. **Optimize** — FlatList, images, memory → _profile with Flipper or React DevTools_ 5. **Test** — Both platforms, real devices ### Error Recovery - **Metro bundler errors** → clear cache with `npx expo start --clear`, then restart - **iOS build fails** → check Xcode logs → resolve native dependency or provisioning issue → rebuild with `npx expo run:ios` - **Android build fails** → check `adb logcat` or Gradle output → resolve SDK/NDK version mismatch → rebuild with `npx expo run:android` - **Native module not found** → run `npx expo install <module>` to ensure compatible version, then rebuild native layers ## Reference Guide Load detailed guidance based on contex

What's inside
Steps it walks through
  1. Core Workflow
  2. Error Recovery
  3. Reference Guide
  4. Constraints
  5. MUST DO
  6. MUST NOT DO
  7. Code Examples
  8. Optimized FlatList with memo + useCallback
  9. KeyboardAvoidingView Form
  10. Platform-Specific Component
  11. Output Format
  12. Knowledge Reference
Ships with 5 files
  • references/expo-router.md
  • references/list-optimization.md
  • references/platform-handling.md
  • references/project-structure.md
  • references/storage-hooks.md
More from claude-skills
All skills →
About this skill
What does the react-native-expert skill do?

Builds, optimizes, and debugs cross-platform mobile applications with React Native and Expo. Implements navigation hierarchies (tabs, stacks, drawers), configures native modules, optimizes FlatList rendering with memo and useCallback, and handles platform-specific code for iOS and Android. Use when building a React Native or Expo mobile app, setting up navigation, integrating native modules, improving scroll performance, handling SafeArea or keyboard input, or configuring Expo SDK projects.

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill react-native-expert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going