Expo Brownfield
expo/skills
Integrate Expo and React Native into an existing native iOS or Android app.
Framework (OSS). An agent skill from arcboxlabs/linkcode.
Install Expo UI
$ npx skills add arcboxlabs/linkcode --skill expo-ui -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install arcboxlabs/linkcode expo-ui --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/arcboxlabs/linkcode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/expo-ui .claude/skills/expo-ui && rm -rf skills-srcUse ~/.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/
Install the "expo-ui" agent skill from https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-ui into .claude/skills/expo-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-ui", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-uiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add arcboxlabs/linkcode --skill expo-ui -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install arcboxlabs/linkcode expo-ui --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arcboxlabs/linkcode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/expo-ui .agents/skills/expo-ui && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "expo-ui" agent skill from https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-ui into .agents/skills/expo-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-ui", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add arcboxlabs/linkcode --skill expo-ui -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install arcboxlabs/linkcode expo-ui --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arcboxlabs/linkcode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/expo-ui .cursor/skills/expo-ui && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "expo-ui" agent skill from https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-ui into .cursor/skills/expo-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-ui", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/arcboxlabs/linkcode.git --path .agents/skills/expo-ui--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add arcboxlabs/linkcode --skill expo-ui -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install arcboxlabs/linkcode expo-ui --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arcboxlabs/linkcode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/expo-ui .gemini/skills/expo-ui && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "expo-ui" agent skill from https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-ui into .gemini/skills/expo-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-ui", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install arcboxlabs/linkcode expo-uiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add arcboxlabs/linkcode --skill expo-ui -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/arcboxlabs/linkcode.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/expo-ui .github/skills/expo-ui && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "expo-ui" agent skill from https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-ui into .github/skills/expo-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-ui", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add arcboxlabs/linkcode --skill expo-ui -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install arcboxlabs/linkcode expo-ui --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arcboxlabs/linkcode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/expo-ui .opencode/skills/expo-ui && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "expo-ui" agent skill from https://github.com/arcboxlabs/linkcode/tree/master/.agents/skills/expo-ui into .opencode/skills/expo-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-ui", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
expo-ui- GitHub stars
- 155
- Token cost
- ~1.2k tokens
- SKILL.md length
- 414 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Framework (OSS). An agent skill from arcboxlabs/linkcode.
- Works in 2 steps: Universal components — start here.… → Platform-specific (SwiftUI / Jetpack…
- Reviewing @expo/ui Host/RNHostView trees
- SKILL.md covers Installation, Choosing an approach (read…, References and Submitting Feedback
- Runs JavaScript scripts from its folder; calls npx
What it does
Expo UI is an agent skill from arcboxlabs/linkcode. Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app. Covers universal cross-platform components (Host, Column, Row, Button, Text, List, and more imported from @expo/ui), drop-in replacements for popular React Native community libraries (BottomSheet, DateTimePicker, Slider, Menu, etc.), and platform-specific SwiftUI (@expo/ui/swift-ui, iOS only) and Jetpack Compose (@expo/ui/jetpack-compose, Android only)…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/drop-in-replacements.md` and `references/jetpack-compose.md`).
It sits in Mobile, covering Cross-platform mobile apps, iOS development and Android development. It works with Expo, Jetpack Compose, Android and iOS. The repository describes itself as: Open-source alternative to Codex App / Workbuddy, supporting Codex, Claude Code, OpenCode, Pi, and Grok Build. Codex App / WorkBuddy 的开源平替，支持 Codex、Claude Code、OpenCode、Pi 和 Grok… The licence is MIT.
When your agent uses it
- Reviewing @expo/ui Host/RNHostView trees
- Building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles
- Choosing between universal and platform-specific components
- Replacing an RN community UI library with a native @expo/ui equivalent
Example prompts
- “/expo-ui”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Bash(node *expo-ui/scripts/list-components.js *)
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Universal components — start here. Import from the @expo/ui root. One component tree runs unmodified on iOS, Android, and web from a…
- Platform-specific (SwiftUI / Jetpack Compose). Import from @expo/ui/swift-ui or @expo/ui/jetpack-compose. Use only when the universal…
What it can do on your machine
Read from SKILL.md and the folder at commit 22c337f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(node *expo-ui/scripts/list-components.js *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
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 UI loads about 1.2k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 247 tokens; SKILL.md has 414 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from arcboxlabs/linkcode at commit 22c337f, republished under its MIT licence (© arcboxlabs). 414 words, ~1,201 tokens.
Download SKILL.mdSave it as
.claude/skills/expo-ui/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- expo-ui
- description
- Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app. Covers universal cross-platform components (Host, Column, Row, Button, Text, List, and more imported from @expo/ui), drop-in replacements for popular React Native community libraries (BottomSheet, DateTimePicker, Slider, Menu, etc.), and platform-specific SwiftUI (@expo/ui/swift-ui, iOS only) and Jetpack Compose (@expo/ui/jetpack-compose, Android only) trees and modifiers. Use when adding or reviewing @expo/ui Host/RNHostView trees, building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles, sections, menus, sheets, pickers, sliders), choosing between universal and platform-specific components, or replacing an RN community UI library with a native @expo/ui equivalent. Not for custom native modules, Expo Router navigation, Reanimated, or data fetching.
- allowed-tools
- Bash(node *expo-ui/scripts/list-components.js *)
- version
- 1.0.0
- license
- MIT
Expo UI (@expo/ui)
@expo/ui renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. Start with its universal components (one tree for iOS, Android, and web) and drop to platform-specific SwiftUI/Jetpack Compose only when the universal layer falls short. It also ships drop-in replacements for migrating off RN community UI libraries.
These instructions track the latest Expo SDK. The universal layer requires SDK 56+. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.
Installation
npx expo install @expo/uiOn SDK 56, @expo/ui works in Expo Go, so npx expo start runs it directly — no custom build required. On older SDKs, build a dev client first (npx expo run:ios / npx expo run:android).
Every @expo/ui tree — universal or platform-specific — must be wrapped in Host.
Choosing an approach (read this first)
Work down this list and stop at the first layer that meets the need:
Universal components — start here. Import from the
@expo/uiroot. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS,react-native-web/react-domon web). No platform file splits. →./references/universal.mdPlatform-specific (SwiftUI / Jetpack Compose). Import from
@expo/ui/swift-uior@expo/ui/jetpack-compose. Use only when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. Downside: you write two trees and split them into.ios.tsx/.android.tsxfiles (or branch onPlatform.OS) — more code to maintain.@expo/ui/swift-uiis iOS-only.@expo/ui/jetpack-composeis Android-only. Importing either in a file that runs on the other platform will crash at runtime with "Unable to get view config" errors. Isolate platform-specific trees in.ios.tsx/.android.tsxfiles placed incomponents/(never insideapp/— Expo Router does not support platform extensions for route files), or guard withPlatform.OSin a regular route file.Hostmust always be imported from@expo/ui(the universal package root), not from the platform-specific sub-packages. →./references/swift-ui.mdand./references/jetpack-compose.md
Show full SKILL.md (86 more words)Show less
Already using an RN community UI library? @expo/ui also ships drop-in replacements — API-compatible swaps for popular libraries (@gorhom/bottom-sheet, @react-native-community/datetimepicker, and more), imported from @expo/ui/community/<name>. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → ./references/drop-in-replacements.md
References
Consult these resources as needed:
references/
universal.md Universal @expo/ui components and when to use them (SDK 56+)
drop-in-replacements.md API-compatible replacements for RN community UI libraries
swift-ui.md Platform-specific iOS UI: @expo/ui/swift-ui components, modifiers, RNHostView, useNativeState
jetpack-compose.md Platform-specific Android UI: @expo/ui/jetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeStateSubmitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes submit-expo-feedback@latest --category skills --subject "expo-ui" "<actionable feedback>"Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
© arcboxlabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts, references) in .agents/skills/expo-ui of arcboxlabs/linkcode.
- SKILL.md
- agents/openai.yaml
- references/drop-in-replacements.md
- references/jetpack-compose.md
- references/swift-ui.md
- references/universal.md
- scripts/list-components.js
Open the folder on GitHubat commit 22c337f
Compare with similar skills
Expo UI 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Expo UI this skillarcboxlabs/linkcode | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Expo Brownfieldexpo/skills | 2.7k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Expo UIexpo/skills | 2.7k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Developing Mobile Appstelagod/code-abyss | 244 | — | ~258 | Automated safety check: Pass | MIT | |
| Senior Mobileborghei/Claude-Skills | 891 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Expo Brownfield Integrationmweinbach/agent-coworker | 156 | 2 repos | ~900 | Automated safety check: Notes | Custom licence |
Similar skills
- Official
- Official
Expo UI
expo/skills
Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android.
Developing Mobile Apps
telagod/code-abyss
Mobile development knowledge reference covering iOS (SwiftUI), Android (Jetpack Compose), React Native, and Flutter.
Senior Mobile
borghei/Claude-Skills
A skill your agent uses when the user asks to "build a mobile app", "scaffold React Native project", "create SwiftUI views", "set up Jetpack Compose", "optimize mobile performance", "configure Expo…
Expo Brownfield Integration
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.
Simdeck
NativeScript/SimDeck
A skill your agent uses for simulator lifecycle, app install/launch, live viewing, UI inspection, touch/keyboard automation, screenshots, recordings, logs, pasteboard, hardware controls, and…
More from arcboxlabs/linkcode
Effect TS
arcboxlabs/linkcode
A skill your agent uses whenever working in a repository that uses Effect, even if the current task is in a new file or the user does not explicitly ask for Effect help.
Expo Native UI
arcboxlabs/linkcode
Framework (OSS). An agent skill from arcboxlabs/linkcode.
Linear
arcboxlabs/linkcode
ArcBox's Linear workflow. An agent skill from arcboxlabs/linkcode.
Related
Categories
Questions about Expo UI
What does Expo UI do?
Framework (OSS). An agent skill from arcboxlabs/linkcode. Expo UI is an agent skill from arcboxlabs/linkcode. Framework (OSS).
When should I use Expo UI?
Expo UI fits situations like: reviewing @expo/ui Host/RNHostView trees; building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles; choosing between universal and platform-specific components; replacing an RN community UI library with a native @expo/ui equivalent.
How do I install Expo UI in Claude Code?
Run `npx skills add arcboxlabs/linkcode --skill expo-ui -a claude-code`. Or copy the skill folder (.agents/skills/expo-ui in arcboxlabs/linkcode) into .claude/skills/expo-ui in your project. Claude Code loads it when a task matches its description.
How do I install Expo UI in Codex?
Run `npx skills add arcboxlabs/linkcode --skill expo-ui -a codex`. Or copy the skill folder (.agents/skills/expo-ui in arcboxlabs/linkcode) into .agents/skills/expo-ui in your project. Codex loads it when a task matches its description.
Can I use Expo UI 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 arcboxlabs/linkcode --skill expo-ui -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-ui, .gemini/skills/expo-ui, .github/skills/expo-ui and .opencode/skills/expo-ui in your project.
What does Expo UI need to run?
Going by SKILL.md and its folder, Expo UI needs JavaScript for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(node *expo-ui/scripts/list-components.js *).
Does Expo UI access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Expo UI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Expo UI use?
Expo UI is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Expo UI use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 3.9k tokens, read only when the agent opens those files.
What are the alternatives to Expo UI?
Skills that share tags, products or a category with Expo UI: Expo Brownfield (expo/skills, 2.7k stars), Expo UI (expo/skills, 2.7k stars), Developing Mobile Apps (telagod/code-abyss, 244 stars) and Senior Mobile (borghei/Claude-Skills, 891 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Expo UI?
arcboxlabs (a GitHub organization) maintains it in arcboxlabs/linkcode, which has 155 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 28, 2026.
Source: arcboxlabs/linkcode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.