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-quick-start.md

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

Skill: Expo Brownfield Quick Start

Configure Expo project for brownfield packaging before iOS/Android host integration.

Quick Command

npm install @callstack/react-native-brownfield

When to Use

  • Expo managed or prebuild project needs brownfield packaging
  • Continuing after expo-create-app.md

Prerequisites

  • Expo project with app.json
  • Expo path selected in router

Step-by-Step Instructions

Progress checklist:
- [ ] Install package
- [ ] Configure plugin
- [ ] Continue to platform integration
  1. Install package in the Expo project.
  2. Add plugin to app.json:
{
  "plugins": ["@callstack/react-native-brownfield"]
}
  1. Optionally add package scripts for packaging/publish commands used by your team.
  2. Continue to exactly one platform file:

Canonical Docs

Common Pitfalls

  • Missing plugin entry in app.json
  • Mixing Expo flow with bare packaging files

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.