AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

react-native-brownfield-migration

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.

Original source
callstackincubator
License
MIT
Pinned revision
59e9d17446a248b21d86f078fcd0bd2d36db1ca4

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read callstackincubator--react-native-brownfield-migration at revision 59e9d17446a248b21d86f078fcd0bd2d36db1ca4, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 13

references/quick-start.md


title: Brownfield Quick Start impact: CRITICAL tags: react-native, brownfield, setup, path-selection, expo, bare

Skill: Brownfield Quick Start

Run shared setup, select one path (Expo or bare), and route immediately to path-specific instructions.

Quick Command

npm install @callstack/react-native-brownfield

When to Use

  • Starting brownfield setup and deciding between Expo and bare RN
  • Preparing project prerequisites before platform-specific packaging

Prerequisites

  • React Native project root identified
  • Node.js and package manager available

Step-by-Step Instructions

Progress checklist:
- [ ] Install package
- [ ] Select Expo or bare path
- [ ] Continue only on selected path
  1. Install package in the React Native app root.
  2. Classify request/project intent:
    • Expo signals: expo, prebuild, Expo plugin workflow
    • Bare signals: direct RN CLI workflow, explicit XCFramework/AAR-only path
  3. Route to exactly one path:
  4. If unclear, ask one disambiguation question and stop.

Stop Conditions

Proceed only if:

  • package install exits with code 0
  • exactly one path is selected

If Failed

  • If install fails, retry with the active package manager and lockfile sync
  • If path intent is ambiguous, stop and ask one Expo vs bare question

Canonical Docs

Common Pitfalls

  • Mixing Expo and bare steps in one flow
  • Starting platform integration before path selection

Related Skills