react-native-expo

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill react-native-expo
0 commentsdiscussion
summary

Build Expo apps with React Native 0.76-0.82+ and SDK 52-55, navigating mandatory New Architecture, React 19 changes, and 16 documented breaking changes.

  • Covers React Native 0.82+ where New Architecture is mandatory and legacy architecture completely removed; includes interop layer guidance for 0.76-0.81 migration path
  • Addresses 16 specific breaking changes including propTypes removal, forwardRef deprecation, Swift iOS template migration, Metro log forwarding removal, and Chrome debugger
skill.md

React Native Expo (0.76-0.82+ / SDK 52+)

Status: Production Ready Last Updated: 2026-01-21 Dependencies: Node.js 20.19.4+, Expo CLI, Xcode 16.1+ (iOS) Latest Versions: [email protected], expo@~54.0.31, [email protected]


Quick Start (15 Minutes)

1. Create New Expo Project (RN 0.76+)

# Create new Expo app with React Native 0.76+
npx create-expo-app@latest my-app

cd my-app

# Install latest dependencies
npx expo install react-native@latest expo@latest

Why this matters:

  • Expo SDK 52+ uses React Native 0.76+ with New Architecture enabled by default
  • New Architecture is mandatory in React Native 0.82+ (cannot be disabled)
  • Hermes is the only supported JavaScript engine (JSC removed from Expo Go)

2. Verify New Architecture is Enabled

# Check if New Architecture is enabled (should be true by default)
npx expo config --type introspect | grep newArchEnabled

CRITICAL:

  • React Native 0.82+ requires New Architecture - legacy architecture completely removed
  • If migrating from 0.75 or earlier, upgrade to 0.76-0.81 first to use the interop layer
  • Never try to disable New Architecture in 0.82+ (build will fail)

3. Start Development Server

# Start Expo dev server
npx expo start

# Press 'i' for iOS simulator
# Press 'a' for Android emulator
# Press 'j' to open React Native DevTools (NOT Chrome debugger!)

CRITICAL:

  • Old Chrome debugger removed in 0.79 - use React Native DevTools instead
  • Metro terminal no longer streams console.log() - use DevTools Console
  • Keyboard shortcuts 'a'/'i' work in CLI, not Metro terminal

Critical Breaking Changes (Dec 2024+)

🔴 New Architecture Mandatory (0.82+)

SDK Timeline:

  • Expo SDK 54 (React Native 0.81): Last release supporting Legacy Architecture
  • Expo SDK 55 (React Native 0.83): New Architecture mandatory, Legacy completely removed

What Changed:

  • 0.76-0.81 / SDK 52-54: New Architecture default, legacy frozen (no new features)
  • 0.82+ / SDK 55+: Legacy Architecture completely removed from codebase

Impact:

# This will FAIL in 0.82+ / SDK 55+:
# gradle.properties (Android)
newArchEnabled=false  # ❌ Ignored, build fails

# iOS
RCT_NEW_ARCH_ENABLED=0  # ❌ Ignored, build fails

Migration Path:

  1. Upgrade to 0.76-0.81 / SDK 54 first (if on 0.75 or earlier)
  2. Test with New Architecture enabled
  3. Fix incompatible dependencies (Redux, i18n, CodePush, Reanimated v3 → v4)
  4. Then upgrade to 0.82+ / SDK 55+

Source: Expo SDK 54 Changelog

🔴 propTypes Removed (React 19 / RN 0.78+)

What Changed: React 19 removed propTypes completely. No runtime validation, no warnings - silently ignored.

Before (Old Code):

import PropTypes from 'prop-types';

function MyComponent({ name, age }) {
  return <Text>{name} is {age}</Text>;
}

MyComponent.propTypes = {  // ❌ Silently ignored in React 19
  name: PropTypes.string.isRequired,
  age: PropTypes.number
};

After (Use TypeScript):

type MyComponentProps = {
  name: string;
  age?: number;
};

function MyComponent({ name, age }: MyComponentProps) {
  return <Text>{name} is {age}</Text>;
}

Migration:

# Use React 19 codemod to remove propTypes
npx @codemod/react-19 upgrade

🔴 forwardRef Deprecated (React 19)

What Changed: forwardRef no longer needed - pass ref as a regular prop.

Before (Old Code):

import { forwardRef } from 'react';

const MyInput = forwardRef((props, ref) => {  // ❌ Deprecated
  return <TextInput ref={ref} {...props} />;
});

After (React 19):

function MyInput({ ref, ...props }) {  // ✅ ref is a regular prop
  return <TextInput ref={ref} {...props} />;
}

🔴 Swift iOS Template Default (0.77+)

What Changed: New projects use Swift AppDelegate.swift instead of Objective-C AppDelegate.mm.

Old Structure:

ios/MyApp/
├── main.m              # ❌ Removed
├── AppDelegate.h       # ❌ Removed
└── AppDelegate.mm      # ❌ Removed

New Structure:

// ios/MyApp/AppDelegate.swift ✅
import UIKit
import React

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
  func application(_ application: UIApplication, ...) -> Bool {
    // App initialization
    return true
  }
}

Migration (0.76 → 0.77): When upgrading existing projects, you MUST add this line:

// Add to AppDelegate.swift during migration
import React
import ReactCoreModules

RCTAppDependencyProvider.sharedInstance()  // ⚠️ CRITICAL: Must add this!

Source: React Native 0.77 Release Notes

🔴 Metro Log Forwarding Removed (0.77+)

What Changed: Metro terminal no longer streams console.log() output.

Before (0.76):

# console.log() appeared in Metro terminal
$ npx expo start
> LOG  Hello from app!  # ✅ Appeared here

After (0.77+):

# console.log() does NOT appear in Metro terminal
$ npx expo start
# (no logs shown)  # ❌ Removed

# Workaround (temporary, will be removed):
$ npx expo start --client-logs  # Shows logs, deprecated

Solution: Use React Native DevTools Console instead (press 'j' in CLI).

Source: React Native 0.77 Release Notes

🔴 Chrome Debugger Removed (0.79+)

What Changed: Old Chrome debugger (chrome://inspect) removed. Use React Native DevTools instead.

Old Method (Removed):

# ❌ This no longer works:
# Open Dev Menu → "Debug" → Chrome DevTools opens

New Method (0.76+):

# Press 'j' in CLI or Dev Menu → "Open React Native DevTools"
# ✅ Uses Chrome DevTools Protocol (CDP)
# ✅ Reliable breakpoints, watch values, stack inspection
# ✅ JS Console (replaces Metro logs)

Limitations:

  • Third-party extensions not yet supported (Redux DevTools, etc.)
  • Network inspector coming in 0.83 (late 2025)

Source: React Native 0.79 Release Notes

🔴 JSC Engine Moved to Community (0.79+)

What Changed: JavaScriptCore (JSC) first-party support removed from React Native 0.81+ core. Moved to community package.

Before (0.78):

  • Both Hermes and JSC bundled in React Native
  • JSC available in Expo Go

After (0.79+ / React Native 0.81+ / SDK 54):

# JSC removed from React Native core
# If you still need JSC (rare):
npm install @react-native-community/javascriptcore

Expo Go:

  • SDK 52+: JSC completely removed from Expo Go
  • Hermes only supported

Note: JSC will eventually be removed entirely from React Native.

Source: Expo SDK 54 Changelog

🔴 Deep Imports Deprecated (0.80+)

What Changed: Importing from internal paths will break.

Before (Old Code):

// ❌ Deep imports deprecated
import Button from 'react-native/Libraries/Components/Button';
import Platform from 'react-native/Libraries/Utilities/Platform';

After:

// ✅ Import only from 'react-native'
import { Button, Platform } from 'react-native';

Source: React Native 0.80 Release Notes

🔴 Android Edge-to-Edge Mandatory (SDK 54+)

What Changed: Edge-to-edge display is enabled in all Android apps by default in SDK 54 and cannot be disabled.

Impact:

// app.json or app.config.js
{
  "expo": {
    "android": {
      // This setting is now IGNORED - edge-to-edge always enabled
      "edgeToEdgeEnabled": false  // ❌ No effect in SDK 54+
    }
  }
}

UI Impact: Content now extends behind system status bar and navigation bar. You must account for insets manually using react-native-safe-area-context.

Solution:

import { SafeAreaView } from 'react-native-safe-area-context';

function App() {
  return 
how to use react-native-expo

How to use react-native-expo on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add react-native-expo
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill react-native-expo

The skills CLI fetches react-native-expo from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/react-native-expo

Reload or restart Cursor to activate react-native-expo. Access the skill through slash commands (e.g., /react-native-expo) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.539 reviews
  • Henry Gill· Dec 24, 2024

    react-native-expo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Pratham Ware· Dec 8, 2024

    Keeps context tight: react-native-expo is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Olivia Chen· Dec 8, 2024

    We added react-native-expo from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Meera Lopez· Dec 4, 2024

    react-native-expo reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Soo Huang· Nov 27, 2024

    Solid pick for teams standardizing on skills: react-native-expo is focused, and the summary matches what you get after install.

  • Lucas Rao· Nov 23, 2024

    I recommend react-native-expo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Henry Desai· Nov 3, 2024

    Keeps context tight: react-native-expo is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Noah Okafor· Oct 18, 2024

    react-native-expo has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Isabella Abbas· Oct 14, 2024

    Useful defaults in react-native-expo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Layla Bansal· Sep 21, 2024

    react-native-expo reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 39

1 / 4