What problem does it solve? Adding React Native to an existing native iOS or Android app requires choosing between shipping a prebuilt AAR/XCFramework or wiring React Native directly into Gradle and CocoaPods, and each path involves intricate build configuration, versioning constraints, and platform-specific pitfalls. ## Core Features & Use Cases - Approach Selection: Decision rules and a comparison matrix for choosing between the isolated approach (prebuilt AAR/XCFramework via expo-brownfield) and the integrated approach (React Native sources added to the existing Gradle/CocoaPods build). - Step-by-Step Integration Guides: Detailed references covering Android Gradle setup, iOS Podfile and Xcode configuration, Swift Package output, fused AAR publishing, and embedding React Native screens via BrownfieldActivity, ReactNativeViewController, or ReactActivity. - Troubleshooting Reference: Solutions for Metro connection failures, XCFramework signing crashes, mavenLocal resolution issues, module name mismatches, and monorepo autolinking problems. - Use Case: An iOS team using Tuist wants to add a React Native onboarding flow without installing Node; the skill guides building an XCFramework with npx expo-brownfield build:ios --package and initializing it with one call in AppDelegate. ## Quick Start Ask the AI to help you add an Expo React Native screen to your existing native iOS or Android app and recommend whether to use the isolated or integrated brownfield approach.