react-native-brownfield-migration — Claude Code skill: what it does
Guides incremental React Native or Expo adoption in native iOS and Android apps using @callstack/react-native-brownfield.
npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a claude-codeWhat react-native-brownfield-migration does
This skill guides step-by-step brownfield integration for existing native iOS and Android codebases using @callstack/react-native-brownfield. It enforces two distinct tracks: Expo or bare React Native. Mixing steps between tracks is strictly disallowed.
The workflow packages React Native artifacts into iOS XCFramework bundles or Android AAR libraries before integrating single surfaces into host applications. Stable settings live in brownfield.config.*, while the native host code stays isolated from direct framework APIs through a facade pattern.
Run this only when the brownfield path is already chosen. Runtime verification depends on agent-device to launch the host app, navigate to the React Native view, and capture screenshots.
What it helps with
- package iOS XCFramework artifacts from React Native source code
- generate and publish Android AAR modules for the native host
- configure brownfield.config settings for repeatable builds
- embed an Expo or React Native surface into an existing native host
Example prompts for the agent
- Set up an iOS XCFramework build using @callstack/react-native-brownfield
- Integrate an Expo brownfield screen into our native Android app
- Help package the bare React Native app as an AAR artifact
How to install react-native-brownfield-migration
1Skills CLI (Vercel)
npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a claude-code2Manually: put the files in place
~/.claude/skills/react-native-brownfield-migration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/react-native-brownfield-migration/
1Skills CLI (Vercel)
npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a codex2Manually: put the files in place
.agents/skills/react-native-brownfield-migration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a cursor2Manually: put the files in place
.cursor/skills/react-native-brownfield-migration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install callstackincubator/agent-skills react-native-brownfield-migration2Manually: put the files in place
.github/skills/react-native-brownfield-migration/SKILL.md1Skills CLI (Vercel)
npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a gemini-cli2Platform CLI
gemini skills install https://github.com/callstackincubator/agent-skills --path skills/react-native-brownfield-migrationManually: put the files in place
.devin/skills/react-native-brownfield-migration/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set4
The whole set →Similar
Questions about react-native-brownfield-migration
How to install react-native-brownfield-migration in Claude Code?
Run npx skills add callstackincubator/agent-skills --skill react-native-brownfield-migration -a claude-code.
What does react-native-brownfield-migration do?
It provides guardrails and step-by-step instructions for packaging React Native or Expo into XCFramework and AAR artifacts, then integrating them into host apps.
What tools are needed to verify the host integration?
The skill uses agent-device to open the host application, navigate to the React Native screen, and collect device screenshots.
Source text
SKILL.md · MIT
--- name: react-native-brownfield-migration description: 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. license: MIT --- # 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](../assess-react-native-migration/SKILL.md) 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: 1. Assess app state and select Expo or bare path. 2. Perform initial setup with `@callstack/react-native-brownfield`. 3. Package RN artifacts (`XCFramework`/`AAR`) from the RN source app. 4. Integrate one RN surface into the host app and validate startup/runtime. 5. Repeat integration by feature/screen for incremental rollout. ## Agent Guardrails (Global) Apply these rules across all reference files: 1. Select one path first (Expo or bare) and do not mix steps. 2. Use placeholders from the docs (`<framework_target_name>`, `<android_module_name>`, `<registered_module_name>`) and resolve from project files. 3. Validate each packaging command before moving to host integration. 4. Run `npx brownfield <command> --help` before relying on any flag table in these references; help output wins. 5. Write stable project settings once into `brownfield.config.*` instead of repeating flags — see [cli-and-config.md][cli-and-config]. 6. Prefer official docs for long platform snippets and CLI option details. 7. Keep host apps isolated from direct React Native APIs when possible (facade approach). 8. 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 - [Quick Start](https://oss.callstack.com/react-native-brownfield/docs/getting-started/quick-start.md) - [Expo Integration](https://oss.callstack.com/react-native-brownfield/docs/getting-started/expo.md) - [iOS Integration](https://oss.callstack.com/react-native-brownfield/docs/getting-started/ios.md) - [Android Integration](https://oss.callstack.com/react-native-brownfield/docs/getting-started/android.md) - [Brownfield CLI](https://oss.callstack.com/react-native-brownfield/docs/cli/brownfield.md) - [Configuration](https://oss.callstack.com/react-native-brownfield/docs/api-reference/configuration.md) - [Guidelines](https://oss.callstack.com/react-native-brownfield/docs/guides/guidelines.md) - [Troubleshooting](https://oss.callstack.com/react-native-brownfield/docs/guides/troubleshooting.md) ## Path Selection Gate (Must Run First) Before selecting any reference file, classify the project: 1. If no React Native app exists yet, use Expo creation path: - [expo-create-app.md][expo-create-app] -> [expo-quick-start.md][expo-quick-start] 2. 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. 3. If still unclear, ask one disambiguation question. 4. 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][quick-start] | Shared preflight and mandatory path-selection gate | | [cli-and-config.md][cli-and-config] | CLI commands, full flag sets, config file, artifact layout, codegen side effects | | [runtime-api.md][runtime-api] | Host <-> RN API surface (JS, Swift, Kotlin) and reference apps | | [expo-create-app.md][expo-create-app] | Scaffold a new Expo app before Expo brownfield setup | | [expo-quick-start.md][expo-quick-start] | Expo plugin setup and packaging readiness | | [expo-ios-integration.md][expo-ios-integration] | Expo iOS packaging and host startup integration | | [expo-android-integration.md][expo-android-integration] | Expo Android packaging, publish, and host integration | | [bare-quick-start.md][bare-quick-start] | Bare React Native baseline setup | | [bare-ios-xcframework-generation.md][bare-ios-xcframework-generation] | Bare iOS XCFramework generation | | [bare-android-aar-generation.md][bare-android-aar-generation] | Bare Android AAR generation and publish | | [bare-ios-native-integration.md][bare-ios-native-integration] | Bare iOS host integration | | [bare-android-native-integration.md][bare-android-native-integration] | Bare Android host integration | ## Problem -> Skill Mapping | Problem | Start With | |---------|------------| | Need migration path decision first | [assess-react-native-migration](../assess-react-native-migration/SKILL.md) | | Need Expo vs bare path decision | [quick-start.md][quick-start] | | Need a CLI flag, the config file shape, or the artifact paths | [cli-and-config.md][cli-and-config] | | Need a host <-> RN API name, signature, or a working example app | [runtime-api.md][runtime-api] | | 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][expo-create-app] | | Need Expo brownfield setup and plugin wiring | [expo-quick-start.md][expo-quick-start] | | Need Expo iOS brownfield integration | [expo-ios-integration.md][expo-ios-integration] | | Need Expo Android brownfield integration | [expo-android-integration.md][expo-android-integration] | | Need bare RN baseline setup | [bare-quick-start.md][bare-quick-start] | | Need bare RN iOS XCFramework generation | [bare-ios-xcframework-generation.md][bare-ios-xcframework-generation] | | Need bare RN Android AAR generation/publish | [bare-android-aar-generation.md][bare-android-aar-generation] | | Need bare RN iOS host integration | [bare-ios-native-integration.md][bare-ios-native-integration] | | Need bare RN Android host integration | [bare-android-native-integration.md][bare-android-native-integration] | ## Related Skills - [Assess React Native migration](../assess-react-native-migration/SKILL.md) 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. [quick-start]: references/quick-start.md [cli-and-config]: references/cli-and-config.md [runtime-api]: references/runtime-api.md [expo-create-app]: references/expo-create-app.md [expo-quick-start]: references/expo-quick-start.md [expo-ios-integration]: references/expo-ios-integration.md [expo-android-integration]: references/expo-android-integration.md [bare-quick-start]: references/bare-quick-start.md [bare-ios-xcframework-generation]: references/bare-ios-xcframework-generation.md [bare-android-aar-generation]: references/bare-android-aar-generation.md [bare-ios-native-integration]: references/bare-ios-native-integration.md [bare-android-native-integration]: references/bare-android-native-integration.md
© callstackincubator · MIT · callstackincubator/agent-skills