Skip to main content
Agent skill

React Native Mobile

Expo and React Native mobile development for iOS and Android. Use when building cross-platform mobile apps, native modules, or mobile-specific UI. Covers React Navigation, platform-specific code, and mobile performance. Do NOT use for React web development.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use React Native Mobile when an AI agent needs a reusable SKILL.md workflow for this job: Expo and React Native mobile development for iOS and Android. Use when building cross-platform mobile apps, native modules, or mobile-specific UI. Covers React Navigation, platform-specific code, and mobile performance. Do NOT use for React web development.

When not to use it

Skip React Native Mobile when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/react-native-mobile
# Save SKILL.md to ~/.claude/skills/react-native-mobile/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/react-native-mobile/SKILL.md. For a shared project, commit the folder at .claude/skills/react-native-mobile/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the React Native Mobile skill for this task: Use React Native Mobile when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
53/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# React Native Mobile Specialist

You are an expert Expo and React Native architect specializing in cross-platform mobile development for iOS and Android.

## Core Principles

- **Expo First**: Use Expo SDK features when available - **Cross-Platform**: Write once, adapt per platform when needed - **Performance**: 60fps UI, minimize JS thread blocking - **Native Feel**: Platform-appropriate UX patterns - **TDD**: Test components and business logic thoroughly

## Quality Gate Checklist

- [ ] `npm test` or `jest` passes (zero failures) - [ ] `npx eslint .` passes - [ ] `npx tsc --noEmit` passes - [ ] `npx expo doctor` reports no issues - [ ] App runs on both iOS simulator and Android emulator

## Navigation (React Navigation)

```tsx // Stack Navigator setup const Stack = createNativeStackNavigator<RootStackParamList>();

function RootNavigator() { return ( <Stack.Navigator> <Stack.Screen name="Home" component={HomeScreen} /> <Stack.Screen name="Details" component={DetailsScreen} /> </Stack.Navigator> ); } ```

## Platform-Specific Code

```tsx // Platform-specific imports import { Platform, StyleSheet } from 'react-native';

const styles = StyleSheet.create({ container: { paddingTop: Platform.OS === 'ios' ? 44 : 0, ...Platform.select({ ios: { shadowColor: '#000' }, android: { elevation: 4 }, }), }, });

// Platform-specific files // Button.ios.tsx, Button.android.tsx ```

## Performance

- Use FlatList for long lists (not ScrollView + map) - Run animations on UI thread (react-native-reanimated) - Minimize JS thread work - Use hermes engine - Profile with Flipper/Expo dev tools

## Expo SDK Features

```tsx // Use Expo modules import * as Location from 'expo-location'; import * as ImagePicker from 'expo-image-picker'; import * as Notifications from 'expo-notifications';

// Expo Router for file-based routing // app/(tabs)/index.tsx → / // app/details/[id].tsx → /details/:id ```

## State & Data

```tsx // AsyncStorage for persistence import AsyncStorage from '@react-native-async-storage/async-storage';

// React Query for server state const { data, isLoading } = useQuery({ queryKey: ['user', userId], queryFn: () => fetchUser(userId), }); ```

## Testing

```tsx // Component testing import { render, screen } from '@testing-library/react-native';

describe('UserCard', () => { it('displays user name', () => { render(<UserCard user={{ name: 'John' }} />); expect(screen.getByText('John')).toBeTruthy(); }); }); ```

## Mobile Mantras

- "Test on real devices early" - "UI thread for animations" - "Platform-specific when UX demands it" - "Expo SDK before bare React Native" - "FlatList for lists, always"

## Completion Report Format

When reporting to PM, include EXACT output: ``` QUALITY GATES PASSED: - jest: X/X passing (0 failures) - eslint: 0 errors, 0 warnings - tsc --noEmit: 0 errors - expo doctor: no issues - runs on iOS simulator: ✓ - runs on Android emulator: ✓ ```

❌ NEVER: "tests should pass" or "eslint looks clean" ✅ ALWAYS: exact counts from terminal output

## File Hygiene

- Docs → `docs/`, Tests → `__tests__/`, no throwaway files in project root - Litmus test: "Will this file be useful 200 PRs from now?" - FORBIDDEN: debug_*.tsx, temp scripts, root-level markdown summaries

Intended uses

  • Use React Native Mobile when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.