expo-ui
An agent skill by expo, from expo/skills. Tags: android, components, design, mobile, swift, ui-ux.
What it does
Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo/ui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom/bottom-sheet, or RN built-in Picker/Switch; use @expo/ui instead. Fall back to RN built-ins only when @expo/ui is missing the component. NOTE: @expo/ui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList/FlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI/Jetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-ui
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/expo-ui ~/.claude/skills/expo-ui
Safety box score
Grade B, low risk: 11 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is a UI guidance package for Expo’s `@expo/ui`, plus a small local Node helper that inspects the installed package. The main risks are limited: it can invoke `npx` to install or run registry packages, and one command can send feedback to Expo over the network; otherwise it stays read-only and scoped to component selection.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | It explicitly runs registry packages with `npx expo install @expo/ui` and `npx --yes submit-expo-feedback@latest ...`; the shipped helper is a plain Node script that only reads local files. |
| Network access | 1 (low) | The `npx` commands contact npm/Expo, and the feedback command sends a subject/message to Expo (`--category skills --subject "expo-ui"`). |
| Filesystem reach | 0 (none) | The helper script only reads `project-path/node_modules/@expo/ui` and its `package.json`; there is no write, delete, or outside-project path access. |
| Secrets & credentials | 0 (none) | There is no handling of tokens, keys, passwords, `.env` files, keychains, or browser sessions, and no request to paste secrets. |
| Privilege & persistence | 0 (none) | No sudo, global install, service registration, scheduled task, or shell/OS setting changes are requested. |
| Instruction hijack surface | 0 (none) | The files do not instruct the agent to ignore safeguards, follow remote instructions, hide actions, or otherwise override its rules. |
| Irreversible actions | 1 (low) | The only autonomous outward action is optional feedback submission to Expo; there is no deploy, publish, payment, or delete workflow. |
| Transparency | 0 (none) | All shipped files are readable markdown, YAML, and JavaScript; there are no binaries or decoded-at-runtime blobs. |
Before installing
- Inspect `SKILL.md` for the two `npx` commands before letting an agent run them.
- Run `scripts/list-components.js <scratch-project>` once and confirm it only reads `node_modules/@expo/ui`.
- If you do not want outbound messages, avoid `npx --yes submit-expo-feedback@latest` or run it only from a disposable account.
Rated 2026-10-20 by an automated review of 7 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-ui/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- expo-native-ui — Framework (OSS). Build beautiful, native-feeling Expo screens.
- expo-design-system — Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow.
- apple-design — Apple's approach to interface design and fluid, physical motion, translated for the web.
- kotlin-specialist — Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction.
- eas-app-stores — EAS service (paid). Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play.
- eas-simulator — EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud.