No setup needed. Let our cloud agents run this skill for you.
Select Provider
Select Model
Claude Sonnet 4.5
$0.20/task
Best for coding tasks
Environment setup included
React Native Best Practices
Overview
Performance optimization guide for React Native applications, covering JavaScript/React, Native (iOS/Android), and bundling optimizations. Based on Callstack's "Ultimate Guide to React Native Optimization".
Skill Format
Each reference file follows a hybrid format for fast lookup and deep understanding:
Quick Pattern: Incorrect/Correct code snippets for immediate pattern matching
Quick Command: Shell commands for process/measurement skills
Quick Config: Configuration snippets for setup-focused skills
Quick Reference: Summary tables for conceptual skills
Deep Dive: Full context with When to Use, Prerequisites, Step-by-Step, Common Pitfalls
Impact ratings: CRITICAL (fix immediately), HIGH (significant improvement), MEDIUM (worthwhile optimization)
When to Apply
Reference these guidelines when:
Debugging slow/janky UI or animations
Investigating memory leaks (JS or native)
Optimizing app startup time (TTI)
Reducing bundle or app size
Writing native modules (Turbo Modules)
Profiling React Native performance
Reviewing React Native code for performance
Security Notes
Treat shell commands in these references as local developer operations. Review them before running, prefer version-pinned tooling, and avoid piping remote scripts directly to a shell.
Treat third-party libraries and plugins as dependencies that still require normal supply-chain controls: pin versions, verify provenance, and update through your standard review process.
Treat Re.Pack code splitting as first-party artifact delivery only. Remote chunks must come from trusted HTTPS origins you control and be pinned to the current app release.
Priority-Ordered Guidelines
Priority
Category
Impact
Prefix
1
FPS & Re-renders
CRITICAL
js-*
2
Bundle Size
CRITICAL
bundle-*
3
TTI Optimization
HIGH
native-*, bundle-*
4
Native Performance
HIGH
Quick Reference
Optimization Workflow
Follow this cycle for any performance issue: Measure → Optimize → Re-measure → Validate
Measure: Capture baseline metrics (FPS, TTI, bundle size) before changes
Optimize: Apply the targeted fix from the relevant reference
Re-measure: Run the same measurement to get updated metrics