What problem does it solve? Choosing and correctly implementing native UI components in Expo apps is error-prone: developers reach for community libraries like @gorhom/bottom-sheet or Reanimated when @expo/ui already provides native SwiftUI/Jetpack Compose equivalents, misuse non-virtualized List for large datasets, or crash apps by importing platform-specific packages on the wrong OS. ## Core Features & Use Cases - Native component selection guidance: Directs you to @expo/ui components (BottomSheet, Switch, Slider, Picker, Menu, FieldGroup, List) instead of RN community libraries, with correct props like isPresented/onDismiss. - Three-layer decision tree: Universal components (SDK 56+, works in Expo Go), platform-specific SwiftUI/Jetpack Compose trees, and drop-in replacements for migrating off community libraries. - Component discovery script: Runs list-components.js against the installed @expo/ui package to enumerate exact components and modifiers available in your SDK version. - Use Case: Building a map screen with a slide-up detail sheet — the Skill provides the correct BottomSheet implementation with snapPoints and Host wrapping, avoiding silent failures from @gorhom-style props. ## Quick Start Ask the assistant to build a native bottom sheet or settings-style grouped list in your Expo app using @expo/ui.