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.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionreact-native-expoExecute the skills CLI command in your project's root directory to begin installation:
Fetches react-native-expo from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate react-native-expo. Access via /react-native-expo in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
697
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
697
stars
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]
# 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:
# Check if New Architecture is enabled (should be true by default)
npx expo config --type introspect | grep newArchEnabled
CRITICAL:
# 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:
console.log() - use DevTools ConsoleSDK Timeline:
What Changed:
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:
Source: Expo SDK 54 Changelog
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
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} />;
}
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
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
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:
Source: React Native 0.79 Release Notes
What Changed: JavaScriptCore (JSC) first-party support removed from React Native 0.81+ core. Moved to community package.
Before (0.78):
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:
Note: JSC will eventually be removed entirely from React Native.
Source: Expo SDK 54 Changelog
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
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 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
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate 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
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
wordpress-elementor
123jezweb/claude-skills
Productivitysame reporeact-vite-best-practices
55asyrafhussin/agent-skills
Frontendtag: reactfrontend-design
633anthropics/claude-code
Frontendsame categoryui-animation
230mblode/agent-skills
Frontendsame categorypremium-frontend-ui
228github/awesome-copilot
Frontendsame categoryhigh-end-visual-design
183leonxlnx/taste-skill
Frontendsame categoryReviews
4.5★★★★★39 reviews- HHenry Gill★★★★★Dec 24, 2024
react-native-expo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- PPratham 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.
- OOlivia Chen★★★★★Dec 8, 2024
We added react-native-expo from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- MMeera Lopez★★★★★Dec 4, 2024
react-native-expo reduced setup friction for our internal harness; good balance of opinion and flexibility.
- SSoo 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.
- LLucas Rao★★★★★Nov 23, 2024
I recommend react-native-expo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- HHenry 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.
- NNoah Okafor★★★★★Oct 18, 2024
react-native-expo has been reliable in day-to-day use. Documentation quality is above average for community skills.
- IIsabella 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.
- LLayla 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 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.