AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

react-native-brownfield-migration

Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts.

Original source
callstackincubator
License
MIT
Pinned revision
59e9d17446a248b21d86f078fcd0bd2d36db1ca4

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read callstackincubator--react-native-brownfield-migration at revision 59e9d17446a248b21d86f078fcd0bd2d36db1ca4, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 13

references/bare-quick-start.md


title: Bare React Native Quick Start impact: CRITICAL tags: react-native, brownfield, bare, setup, cocoapods, gradle

Skill: Bare React Native Quick Start

Prepare a bare React Native project for brownfield packaging and host integration.

Quick Command

npm install @callstack/react-native-brownfield
cd ios && pod install && cd ..

When to Use

  • User explicitly chooses bare React Native path
  • Project directly manages native iOS/Android folders

Prerequisites

  • Bare RN app with working ios/ and android/
  • CocoaPods and Gradle working

Step-by-Step Instructions

Progress checklist:
- [ ] Install package
- [ ] Install pods
- [ ] Create brownfield config
- [ ] Continue to bare platform packaging
  1. Install package in RN app root.
  2. Run pod install for iOS.
  3. Create brownfield.config.js or brownfield.config.json with the iOS scheme and the Android module name and variant, so packaging commands stay short — see cli-and-config.md.
  4. Continue with one platform packaging file:

Canonical Docs

Common Pitfalls

  • Starting packaging before pod install
  • Mixing Expo-only startup APIs into bare flow

Related Skills