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
Fetches react-native-expo from jezweb/claude-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/react-native-expo
Restart Cursor to activate react-native-expo. Access via /react-native-expo in your agent's command palette.
⚠
Security 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 environment. Always review source, verify the publisher, and test in isolation before production.
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).
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.
›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
