skilld
All skills
callstackincubator avatar

/react-native-brownfield-migration

@fa0bad0 official
by Callstack Incubatorcallstackincubator/agent-skills1.7k stars
118

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.

Ask your Agent

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

This session only. Nothing lands on disk.

referencesbare-ios-xcframework-generation.md

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

Skill: Bare iOS XCFramework Generation

Package a bare React Native app into XCFramework artifacts for native iOS host consumption.

Quick Command

npx brownfield package:ios --scheme <framework_target_name> --configuration Release

When to Use

  • Building iOS artifacts from a bare RN app
  • Rebuilding XCFramework after RN/native dependency updates

Prerequisites

  • bare-quick-start.md completed
  • Framework target exists in ios/*.xcworkspace
  • Podfile includes framework target with inherit! :complete
  • If running pod install directly, static linking is configured as recommended in iOS integration docs
  • Framework target build settings:
    • Build Libraries for Distribution = YES
    • User Script Sandboxing = NO
    • Skip Install = NO
    • Enable Module Verifier = NO

Step-by-Step Instructions

Progress checklist:
- [ ] Framework target + Podfile ready
- [ ] Bundle script present on framework target
- [ ] Public interface file exports ReactBrownfield
- [ ] package:ios succeeds
- [ ] Artifacts validated
  1. Create or verify framework target in Xcode workspace.
    • If target folders are folder references, convert them to groups (per iOS integration docs).
  2. Ensure Podfile has nested framework target and run pod install.
  3. Ensure framework target includes Bundle React Native code and images run script with expected input files ($(SRCROOT)/.xcode.env.local, $(SRCROOT)/.xcode.env).
  4. Add framework interface file:
@_exported import ReactBrownfield
public let ReactNativeBundle = Bundle(for: InternalClassForBundle.self)
class InternalClassForBundle {}
  1. Package framework:
    • npx brownfield package:ios --scheme <framework_target_name> --configuration Release
  2. Validate output directory produced by command (commonly ios/.brownfield/package or .brownfield/ios/package):
    • <framework_target_name>.xcframework
    • ReactBrownfield.xcframework
    • hermesvm.xcframework (or hermes.xcframework for older RN)

Stop Conditions

Proceed only if:

  • package command exits with code 0
  • all required frameworks are present in package output

If Failed

  • Re-run pods and retry package command
  • Re-check framework target build settings and run script phase
  • Do not proceed to host integration until artifacts are complete

Canonical Docs

Common Pitfalls

  • Packaging app target instead of framework target
  • Missing bundle run script on framework target
  • Incomplete framework set linked into host app

Related Skills

Source: SKILL.md on GitHub

Third-party checks

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

Provenance

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

Topics

  • react-native
  • brownfield
  • expo
  • ios
  • android
  • xcframework
  • aar
  • native-integration
  • migration

README badge

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

What it does

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.

Frequently asked

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.