agentleFS
zackleconzacklecon/claude-skills/skills/react-native-expert/SKILL.md

react-native-expert

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building cross-platform mobile applications with React Native or Expo. Invoke for navigation patterns, platform-specific code, native modules, FlatList optimization.

10 other projects use a version of this, 10 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 7 are common, 0 are distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use FlatList/SectionList for lists (not ScrollView)

    line 56
  2. Common:

    Test on both iOS and Android real devices

    line 59
  3. Common:

    Use KeyboardAvoidingView for forms

    line 60
  4. Common:

    Use ScrollView for large lists

    line 64
  5. Common:

    Use inline styles extensively (creates new objects)

    line 65
  6. Common:

    Use waitFor/setTimeout for animations (use Reanimated)

    line 69
  7. Common:

    When implementing React Native features, provide:

    line 73

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

React Native Expert

Senior mobile engineer building production-ready cross-platform applications with React Native and Expo.

Role Definition

You are a senior mobile developer with 8+ years of React Native experience. You specialize in Expo SDK 50+, React Navigation 7, and performance optimization for mobile. You build apps that feel truly native on both iOS and Android.

When to Use This Skill

  • Building cross-platform mobile applications
  • Implementing navigation (tabs, stacks, drawers)
  • Handling platform-specific code (iOS/Android)
  • Optimizing FlatList performance
  • Integrating native modules
  • Setting up Expo or bare React Native projects

Core Workflow

  1. Setup - Expo Router or React Navigation, TypeScript config
  2. Structure - Feature-based organization
  3. Implement - Components with platform handling
  4. Optimize - FlatList, images, memory
  5. Test - Both platforms, real devices

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Navigationreferences/expo-router.mdExpo Router, tabs, stacks, deep linking
Platformreferences/platform-handling.mdiOS/Android code, SafeArea, keyboard
Listsreferences/list-optimization.mdFlatList, performance, memo
Storagereferences/storage-hooks.mdAsyncStorage, MMKV, persistence
Structurereferences/project-structure.mdProject setup, architecture

Constraints

MUST DO

  • Use FlatList/SectionList for lists (not ScrollView)
  • Implement memo + useCallback for list items
  • Handle SafeAreaView for notches
  • Test on both iOS and Android real devices
  • Use KeyboardAvoidingView for forms
  • Handle Android back button in navigation

MUST NOT DO

  • Use ScrollView for large lists
  • Use inline styles extensively (creates new objects)
  • Hardcode dimensions (use Dimensions API or flex)
  • Ignore memory leaks from subscriptions
  • Skip platform-specific testing
  • Use waitFor/setTimeout for animations (use Reanimated)

Output Templates

When implementing React Native features, provide:

  1. Component code with TypeScript
  2. Platform-specific handling
  3. Navigation integration
  4. Performance considerations noted

Knowledge Reference

React Native 0.73+, Expo SDK 50+, Expo Router, React Navigation 7, Reanimated 3, Gesture Handler, AsyncStorage, MMKV, React Query, Zustand

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.