All skills
callstackincubator avatar

/react-native-brownfield-migration

@fa0bad0 official

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.

Use this Skill: https://skilld.dev/gh/callstackincubator/agent-skills/react-native-brownfield-migration

This session only. Nothing lands on disk.

referencesexpo-android-integration.md

≈792 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Skill: Expo Android Integration

Package and publish Expo Android AAR, then initialize host runtime and mount RN UI.

Quick Command

npx brownfield package:android --module-name <android_module_name> --variant release
npx brownfield publish:android --module-name <android_module_name>

When to Use

  • User requests Expo Android brownfield integration
  • Host app must consume Expo-backed RN AAR

Prerequisites

  • expo-quick-start.md completed
  • Android host app builds and syncs
  • Android module name resolved (brownfieldlib by default unless overridden in Expo plugin options)

Agent-Assisted Verification

Use agent-device after the host build succeeds. Read the agent-device skill or CLI help when available before exact commands. 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. Then open the host app, navigate to the Expo-backed RN surface, capture snapshots/screenshots, and collect logs for runtime behavior.

Step-by-Step Instructions

Progress checklist:
- [ ] Package AAR
- [ ] Publish to Maven local
- [ ] Initialize host runtime
- [ ] Render RN module
  1. Build AAR:
    • npx brownfield package:android --module-name <android_module_name> --variant release
  2. Publish to Maven local:
    • npx brownfield publish:android --module-name <android_module_name>
  3. Initialize runtime in Activity or Application:
ReactNativeHostManager.initialize(application) {
  Toast.makeText(this, "React Native has been loaded", Toast.LENGTH_LONG).show()
}
  1. Forward configuration changes:
override fun onConfigurationChanged(newConfig: Configuration) {
    super.onConfigurationChanged(newConfig)
    ReactNativeHostManager.onConfigurationChanged(application, newConfig)
}
  1. Render RN UI with JS-registered module name:
    • ReactNativeFragment.createReactNativeFragment("<registered_module_name>")
    • or ReactNativeBrownfield.shared.createView(context, activity, "<registered_module_name>")

Stop Conditions

Mark complete only if:

  • package and publish commands both exit with code 0
  • host app resolves published dependency and renders module
  • device evidence is captured with agent-device when possible

Canonical Docs

Common Pitfalls

  • Using ComponentActivity with Expo (use AppCompatActivity)
  • Missing ReactNativeHostManager.initialize(...) before UI creation
  • Module name mismatch with AppRegistry.registerComponent

Related Skills

Source: SKILL.md on GitHub

No alerts17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill provides a workflow for migrating native mobile applications to React Native using the @callstack/react-native-brownfield library. It uses standard development tools, package managers, and vendor-provided CLI tools. No malicious patterns, obfuscation, or unauthorized data exfiltration were detected.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    8/12 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at fa0bad0. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Activeupdated 2 months ago
  • react-native
  • brownfield
  • expo
  • ios
  • android
  • xcframework
  • aar
  • native-integration
  • migration

README badge

README badge for callstackincubator/agent-skills/react-native-brownfield-migration

Guides incremental adoption of React Native or Expo in existing native iOS and Android apps using @callstack/react-native-brownfield, covering initial setup, artifact packaging (XCFramework and AAR), and phased host app integration. Targets brownfield migration workflows where React Native surfaces are introduced into established native codebases.

Generated from the current SKILL.md.

Does this skill work with both Expo and bare React Native?
Yes. The skill provides separate tracks for Expo and bare React Native migration. You select one path based on your project state and do not mix steps between them.
What platforms does this skill target?
iOS and Android. For iOS it handles XCFramework generation and integration; for Android it handles AAR generation, publishing, and integration.
Can I use this skill to migrate an existing native app incrementally?
Yes. The skill prescribes a phased approach: assess your app, set up React Native via @callstack/react-native-brownfield, package artifacts, integrate one RN surface into the host app, then repeat by feature for incremental rollout.
Do I need to create a new React Native app first?
Only if you don't have one yet. If you're adding React Native to an existing native app, the skill assumes your host app is already present. If starting from scratch, the skill includes a path to scaffold a new Expo app before brownfield setup.
What happens if I'm unsure whether to use Expo or bare React Native?
The skill includes a path-selection gate that runs first. If your project state is ambiguous, the skill asks one disambiguating question before proceeding with exactly one track.

Generated from the current SKILL.md. These answers refresh after source changes.