More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Expo UI: Real Native Controls, Not Re-implementations

    1

    Build screens from real native UI with @expo/ui: the layer model, component-selection rules, the Host contract, drop-in replacements, and platform-specific trees.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Expo UI: Real Native Controls, Not Re-implementations

    Expo UI: Real Native Controls, Not Re-implementations

    Example session with this skill installed

    Build me an event detail screen with @expo/ui: venue details in a sheet, share actions, notification toggles, fixed info rows, and a long attendee list. One tree if possible.

    • Read your context and instructions
    • Compiled the expo ui

    Event detail screen — built with the skill, one universal tree

    Layer choice: universal, no platform split — nothing on this screen needs platform-specific behavior, and the only difference between platforms is cosmetic.

    Controls mapped: venue map-pin details in a BottomSheet at half detent (isPresented / onDismiss, snapPoints: 'half'); "Add to calendar / Share / Report" as a Menu; notification toggles as @expo/ui Switch rows inside a FieldGroup; the three fixed info rows (date, venue, price) as List + ListItem. The attendee list — hundreds of rows, unknown length — is a FlashList, not the native List: a grouped List would create hundreds of native nodes and the cost would arrive all at once on the user's device.

    Host contract: one Host at the top of the native subtree, wrapping the sheet, menu, switches, and list rows. The sheet's half detent was chosen over full because the map must stay visible behind it — the venue location is the context the actions depend on. No platform-specific imports anywhere near the route file. The screen runs in Expo Go on SDK 56 with no custom build. Rubric score: 9/10 — one point held back because the web default rendering was not opened during the demo; it is a stated follow-up, not an assumption.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    @expo/ui renders actual native interface from React — SwiftUI on iOS, Jetpack Compose on Android — and it exists so you stop re-implementing platform controls badly. This skill teaches the layer model: universal components first (one tree, all platforms), platform-specific trees only when the universal layer lacks a load-bearing modifier, and drop-in replacements as a migration side-path, never a design choice for new code. It covers the Host contract (every native tree wrapped, one Host per subtree), the component-selection rules that matter most — BottomSheet over custom sheets, List for fixed small groups but never for long data, since it is not virtualized — and the migration audit that catches props that silently do nothing after a swap.

    You get a selection decision table, a universal-tree screen template, a native UI checklist, and a scoring rubric with a ship threshold of 8/10. Edge cases cover the sheet that ignores its props, the list that works in development and dies in production, the platform import hiding in a route file, and the missing Host that renders nothing. A worked example builds an event detail screen — half-detent sheet, menu actions, switch rows, fixed info rows, and a FlashList for hundreds of attendees — in one universal tree, running in Expo Go.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    • It assumes SDK 56+; earlier SDKs do not have the universal layer.
    • It is not a styling system — @expo/ui is native controls, not a design system.
    • The List component is not virtualized; the skill's selection rules exist precisely because of that.
    • Platform-specific trees cost two implementations; the skill says when that cost is justified, not how to eliminate it.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Software
    expoNode.js

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Because the OS already ships these controls, and the native ones come with the platform's gestures, accessibility, and animations built in. A styled view pretending to be a switch is a re-implementation — and re-implementations are where the bugs live.

    Only when the universal layer lacks a component or modifier you genuinely need, or you need platform-specific behavior. A cosmetic difference is not a reason to split — two trees for a padding value is maintenance cost for nothing.

    Almost certainly the old community props (`isOpen`, snap-point indices) are still in the code. They silently do nothing in @expo/ui. The migration audit exists for this: every old prop gets checked against the new API and marked kept, renamed, or dropped with a reason.

    New in Mobile Development