react-native-brownfield-migration

Original：🇺🇸 English

Translated

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.

8installs

Sourceilteoood/harness

Added on2026-10-24

NPX Install

npx skill4agent add ilteoood/harness react-native-brownfield-migration

SKILL.md Content

View Translation Comparison →

Migrating to React Native

Use this skill only after the decision to adopt brownfield migration has been made. When the user is still choosing between brownfield, greenfield, a checkpoint-based path, defer, or no migration, use assess-react-native-migration first.

Overview

Prescriptive workflow for incremental adoption of React Native in existing native apps using

@callstack/react-native-brownfield

, from initial setup through phased host integration.

Expo track
Bare React Native track

Use one track per task unless the user explicitly asks for migration or comparison.

Migration Strategy

Use this strategy for brownfield migration planning and execution:

Assess app state and select Expo or bare path.
Perform initial setup with
```
@callstack/react-native-brownfield
```
.
Package RN artifacts (
```
XCFramework
```
/
```
AAR
```
) from the RN source app.
Integrate one RN surface into the host app and validate startup/runtime.
Repeat integration by feature/screen for incremental rollout.

Agent Guardrails (Global)

Apply these rules across all reference files:

Select one path first (Expo or bare) and do not mix steps.

Use placeholders from the docs (

<framework_target_name>

,

<android_module_name>

,

<registered_module_name>

) and resolve from project files.

Validate each packaging command before moving to host integration.
Run
```
npx brownfield <command> --help
```
before relying on any flag table in these references; help output wins.
Write stable project settings once into
```
brownfield.config.*
```
instead of repeating flags — see cli-and-config.md.
Prefer official docs for long platform snippets and CLI option details.
Keep host apps isolated from direct React Native APIs when possible (facade approach).
For startup/runtime verification, use
```
agent-device
```
to open the host app, navigate to the RN surface, capture snapshots/screenshots, and collect device evidence. If it is missing and verification needs it, install it through the environment's approved/trusted path or ask the user to install or enable it.

Canonical Docs

Path Selection Gate (Must Run First)

Before selecting any reference file, classify the project:

If no React Native app exists yet, use Expo creation path:
- expo-create-app.md -> expo-quick-start.md
If React Native app exists, inspect
```
package.json
```
and
```
app.json
```
:
- Expo if
```
expo
```
  is present or Expo plugin workflow is requested.
- Bare RN if native folders and direct RN CLI workflow are used without Expo path requirements.
If still unclear, ask one disambiguation question.
Continue with exactly one path.

When to Apply

Reference this package when:

Implementing an accepted incremental migration from native-only apps to React Native or Expo
Creating brownfield integration flows for Expo or bare React Native projects
Performing initial setup with
```
@callstack/react-native-brownfield
```
Generating iOS XCFramework artifacts from a React Native app
Generating and publishing Android AAR artifacts from a React Native app
Integrating generated artifacts into host iOS/Android apps

Quick Reference

File	Description
quick-start.md	Shared preflight and mandatory path-selection gate
cli-and-config.md	CLI commands, full flag sets, config file, artifact layout, codegen side effects
runtime-api.md	Host <-> RN API surface (JS, Swift, Kotlin) and reference apps
expo-create-app.md	Scaffold a new Expo app before Expo brownfield setup
expo-quick-start.md	Expo plugin setup and packaging readiness
expo-ios-integration.md	Expo iOS packaging and host startup integration
expo-android-integration.md	Expo Android packaging, publish, and host integration
bare-quick-start.md	Bare React Native baseline setup
bare-ios-xcframework-generation.md	Bare iOS XCFramework generation
bare-android-aar-generation.md	Bare Android AAR generation and publish
bare-ios-native-integration.md	Bare iOS host integration
bare-android-native-integration.md	Bare Android host integration

Problem -> Skill Mapping

Problem	Start With
Need migration path decision first	assess-react-native-migration
Need Expo vs bare path decision	quick-start.md
Need a CLI flag, the config file shape, or the artifact paths	cli-and-config.md
Need a host <-> RN API name, signature, or a working example app	runtime-api.md
Need shared state between host and RN, or typed RN -> native navigation	`brownie` / `brownfield-navigation` skills
Need to create a new Expo app for brownfield	expo-create-app.md
Need Expo brownfield setup and plugin wiring	expo-quick-start.md
Need Expo iOS brownfield integration	expo-ios-integration.md
Need Expo Android brownfield integration	expo-android-integration.md
Need bare RN baseline setup	bare-quick-start.md
Need bare RN iOS XCFramework generation	bare-ios-xcframework-generation.md
Need bare RN Android AAR generation/publish	bare-android-aar-generation.md
Need bare RN iOS host integration	bare-ios-native-integration.md
Need bare RN Android host integration	bare-android-native-integration.md

Related Skills

Assess React Native migration before selecting the migration path.
```
brownie
```
(shared host <-> RN state) and
```
brownfield-navigation
```
(typed RN -> native navigation) ship from another repo: invoke them by name, and fall back to the canonical docs if they are not installed.