Agent skill

Expo Brownfield Integration

by mweinbach in mweinbach/agent-coworker

Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.

Custom licenceAuto-check: notesMobile

Install Expo Brownfield Integration

skills CLI
$ npx skills add mweinbach/agent-coworker --skill expo-brownfield -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mweinbach/agent-coworker expo-brownfield --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/mobile/.agents/skills/expo-brownfield .claude/skills/expo-brownfield && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
expo-brownfield
GitHub stars
156
Used in
2 other repos
Token cost
~900 tokens
SKILL.md length
376 words
Files
5 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
Custom licence

At a glance

Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.

  • Embedding React Native screens in an existing Kotlin or Swift app
  • SKILL.md covers Pick an approach, References, Shared prerequisites and Versioning note
  • Calls npx and gem
  • Deciding whether the native team should consume React Native as a library

What it does

A brownfield app is an existing native app that adopts React Native step by step, unlike a greenfield app that starts with it. The skill separates two approaches. The isolated approach ships a prebuilt AAR or XCFramework, so the native team needs no Node or React Native tooling and the code can sit in another repository. The integrated approach adds React Native sources to the existing Gradle and CocoaPods builds, suits a single team that owns both sides, and keeps hot reload and source maps working.

Short rules point the agent to the right path, and four reference files hold the detail: one for each approach, a comparison with decision criteria and scenarios, and a troubleshooting file for Metro connection, build, signing and module-resolution problems. The isolated notes name BrownfieldActivity, ReactNativeViewController and ReactNativeView, and the integrated notes cover ReactActivity, RCTRootView and the Podfile.

When your agent uses it

  • Embedding React Native screens in an existing Kotlin or Swift app
  • Deciding whether the native team should consume React Native as a library
  • Fixing Metro connection or signing problems in a brownfield build

Example prompts

  • “Our Android app is all Kotlin. Add an Expo screen to it without making the native team install Node.”
  • “Compare the isolated and integrated brownfield approaches for our iOS app and recommend one.”
  • “Build the React Native side as an XCFramework and wire it into the Swift app.”

Requirements

  • An existing native iOS or Android project
  • React Native and Expo tooling in the environment that builds the React Native side

What it can do on your machine

Read from SKILL.md and the folder at commit aab9dc6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • gem

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.expo.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Expo Brownfield Integration loads about 900 tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 376 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~900
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:44
    tionally requires **CocoaPods** on iOS (`sudo gem install cocoapods`). The isolated approach does **not** require CocoaP

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 376 words (~900 tokens).

“A brownfield app is an existing native iOS or Android app that adopts React Native incrementally, as opposed to a greenfield app that is React Native from day one.”

— opening of SKILL.md by mweinbach, Custom licence
name
expo-brownfield

Read the full SKILL.md on GitHub

Files

SKILL.md and 4 other files (references) in apps/mobile/.agents/skills/expo-brownfield of mweinbach/agent-coworker.

  • SKILL.md
  • references/brownfield-integrated.md
  • references/brownfield-isolated.md
  • references/comparison.md
  • references/troubleshooting.md

Open the folder on GitHubat commit aab9dc6

Used in 2 other repositories

We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in mweinbach/agent-coworker, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Expo Brownfield Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Expo Brownfield Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Expo Brownfield Integration this skillmweinbach/agent-coworker1562 repos~900Automated safety check: NotesCustom licence
Expo Brownfieldexpo/skills2.7k—~1.4kAutomated safety check: PassMIT
Simulator Audio E2Ehyochan/react-native-nitro-sound961—~1.1kAutomated safety check: PassMIT
Expo UIarcboxlabs/linkcode155—~1.2kAutomated safety check: PassMIT
Moq Kitsoftware-mansion-labs/skills291—~5kAutomated safety check: PassApache-2.0
Web To Mobilesuntay44/web-to-mobile-magic-plugin107—~781Automated safety check: PassMIT

Similar skills

  • Expo Brownfield

    expo/skills

    Official

    Integrate Expo and React Native into an existing native iOS or Android app.

    2.7k GitHub stars~1.4k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Simulator Audio E2E

    hyochan/react-native-nitro-sound

    Build and run repeatable react-native-nitro-sound recorder/player regression tests on an iOS Simulator or Android emulator, with explicit virtual-device selection, microphone permission, Maestro…

    961 GitHub stars~1.1k tokensUpdated 11 days ago
    MobileAuto-check passed
  • Expo UI

    arcboxlabs/linkcode

    Framework (OSS). An agent skill from arcboxlabs/linkcode.

    155 GitHub stars~1.2k tokensUpdated 13 days ago
    MobileAuto-check passed
  • Moq Kit

    software-mansion-labs/skills

    Software Mansion's moq-kit — native Swift (iOS) and Kotlin (Android) SDKs for Media over QUIC (moq-lite) live streaming: sub-second-latency playback, camera/microphone/screen publishing, and…

    291 GitHub stars~5k tokensUpdated 13 days ago
    MobileAuto-check passed
  • Web To Mobile

    suntay44/web-to-mobile-magic-plugin

    Orchestrate website or web app conversion into a mobile app.

    107 GitHub stars~781 tokensUpdated 27 days ago
    MobileAuto-check passed
  • React Native Expert

    Jeffallan/claude-skills

    Builds React Native and Expo apps for iOS and Android: Expo Router navigation, FlatList tuning, platform-specific code and build error recovery.

    12k GitHub stars~1.7k tokensUpdated 7 days ago
    MobileAuto-check passed

More from mweinbach/agent-coworker

All 8 skills in this repo
  • AI Elements Chat Components

    mweinbach/agent-coworker

    Adds AI Elements components such as conversations, messages, tool displays and prompt inputs to a Next.js project that uses shadcn/ui.

    156 GitHub starsUsed in 5 repos~1.8k tokens
    Auto-check passed
  • Use Dom

    mweinbach/agent-coworker

    Use Expo DOM components to run web code in a webview on native and as-is on web.

    156 GitHub starsUsed in 5 repos~2.4k tokens
    Auto-check passed
  • Bun Runtime and Toolkit

    mweinbach/agent-coworker

    Quick reference for using Bun to run TypeScript and JavaScript, install packages, bundle code, run tests and serve HTTP, with the key files and commands.

    156 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check: notes
  • Workflow

    mweinbach/agent-coworker

    Author and run a deterministic multi-agent workflow — a JavaScript script that fans out, pipelines, loops, and judges across many child agents.

    156 GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed
  • Improve Animations

    mweinbach/agent-coworker

    Audit a codebase's animation and motion, produce prioritized improvement plans, and execute selected plans when requested.

    156 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed
  • Memories

    mweinbach/agent-coworker

    A skill your agent uses when the user asks to view, list, inspect, add, create, edit, correct, update, or manage long-term memories for the current chat or workspace.

    156 GitHub stars~547 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Expo Brownfield Integration

What does Expo Brownfield Integration do?

Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build. A brownfield app is an existing native app that adopts React Native step by step, unlike a greenfield app that starts with it. The skill separates two approaches.

When should I use Expo Brownfield Integration?

Expo Brownfield Integration fits situations like: embedding React Native screens in an existing Kotlin or Swift app; deciding whether the native team should consume React Native as a library; fixing Metro connection or signing problems in a brownfield build.

How do I install Expo Brownfield Integration in Claude Code?

Run `npx skills add mweinbach/agent-coworker --skill expo-brownfield -a claude-code`. Or copy the skill folder (apps/mobile/.agents/skills/expo-brownfield in mweinbach/agent-coworker) into .claude/skills/expo-brownfield in your project. Claude Code loads it when a task matches its description.

How do I install Expo Brownfield Integration in Codex?

Run `npx skills add mweinbach/agent-coworker --skill expo-brownfield -a codex`. Or copy the skill folder (apps/mobile/.agents/skills/expo-brownfield in mweinbach/agent-coworker) into .agents/skills/expo-brownfield in your project. Codex loads it when a task matches its description.

Can I use Expo Brownfield Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mweinbach/agent-coworker --skill expo-brownfield -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/expo-brownfield, .gemini/skills/expo-brownfield, .github/skills/expo-brownfield and .opencode/skills/expo-brownfield in your project.

What does Expo Brownfield Integration need to run?

Going by SKILL.md and its folder, Expo Brownfield Integration needs the command-line tools its instructions call (npx and gem). Our summary lists: An existing native iOS or Android project; React Native and Expo tooling in the environment that builds the React Native side.

Does Expo Brownfield Integration access the network?

SKILL.md names 1 domain. As links in the text: docs.expo.dev. This is read from the text; nothing was executed.

Is Expo Brownfield Integration safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Expo Brownfield Integration use?

Expo Brownfield Integration has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Expo Brownfield Integration use?

About 900 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Expo Brownfield Integration?

Skills that share tags, products or a category with Expo Brownfield Integration: Expo Brownfield (expo/skills, 2.7k stars), Simulator Audio E2E (hyochan/react-native-nitro-sound, 961 stars), Expo UI (arcboxlabs/linkcode, 155 stars) and Moq Kit (software-mansion-labs/skills, 291 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Expo Brownfield Integration?

mweinbach (a GitHub user) maintains it in mweinbach/agent-coworker, which has 156 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

Source: mweinbach/agent-coworker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.