react-native-brownfield-migration

callstackincubator/agent-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/callstackincubator/agent-skills --skill react-native-brownfield-migration
0 commentsdiscussion
summary

Prescriptive workflow for incremental adoption of React Native in existing native apps using @callstack/react-native-brownfield, from initial setup through phased host integration.

skill.md

Migrating to React Native

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. Prefer official docs for long platform snippets and CLI option details.
  5. Keep host apps isolated from direct React Native APIs when possible (facade approach).

Canonical Docs

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:
  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:

  • Planning 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 Shared preflight and mandatory path-selection gate
expo-create-app.md Scaffold a new Expo app before Expo brownfield setup
expo-quick-start.md Expo plugin setup and packaging readiness
expo-ios-integration.md Expo iOS packaging and host startup integration
expo-android-integration.md Expo Android packaging, publish, and host integration
bare-quick-start.md Bare React Native baseline setup
bare-ios-xcframework-generation.md Bare iOS XCFramework generation
bare-android-aar-generation.md Bare Android AAR generation and publish
bare-ios-native-integration.md Bare iOS host integration
bare-android-native-integration.md Bare Android host integration

Problem -> Skill Mapping

Problem Start With
Need path decision first quick-start.md
Need to create a new Expo app for brownfield expo-create-app.md
Need Expo brownfield setup and plugin wiring expo-quick-start.md
Need Expo iOS brownfield integration expo-ios-integration.md
Need Expo Android brownfield integration expo-android-integration.md
Need bare RN baseline setup bare-quick-start.md
Need bare RN iOS XCFramework generation bare-ios-xcframework-generation.md
Need bare RN Android AAR generation/publish bare-android-aar-generation.md
Need bare RN iOS host integration bare-ios-native-integration.md
Need bare RN Android host integration bare-android-native-integration.md
how to use react-native-brownfield-migration

How to use react-native-brownfield-migration on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add react-native-brownfield-migration
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/callstackincubator/agent-skills --skill react-native-brownfield-migration

The skills CLI fetches react-native-brownfield-migration from GitHub repository callstackincubator/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/react-native-brownfield-migration

Reload or restart Cursor to activate react-native-brownfield-migration. Access the skill through slash commands (e.g., /react-native-brownfield-migration) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.729 reviews
  • James Abebe· Dec 24, 2024

    Registry listing for react-native-brownfield-migration matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Shikha Mishra· Dec 20, 2024

    react-native-brownfield-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Lucas Abebe· Nov 15, 2024

    Useful defaults in react-native-brownfield-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yash Thakker· Nov 11, 2024

    react-native-brownfield-migration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Lucas Brown· Oct 14, 2024

    Solid pick for teams standardizing on skills: react-native-brownfield-migration is focused, and the summary matches what you get after install.

  • Benjamin Mensah· Oct 6, 2024

    I recommend react-native-brownfield-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Dhruvi Jain· Oct 2, 2024

    Keeps context tight: react-native-brownfield-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Xiao Choi· Sep 1, 2024

    Registry listing for react-native-brownfield-migration matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Xiao Robinson· Aug 20, 2024

    react-native-brownfield-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Anika Haddad· Jul 11, 2024

    I recommend react-native-brownfield-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 29

1 / 3