expo-overview

Routes Expo and React Native tasks to the correct expo-* or eas-* skill via decision tree.

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill expo-overview-aibiz-automatyzacje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-overview
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/expo-overview
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill expo-overview-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working in an Expo (React Native) project, it is hard to know which of the 16 specialized expo-/eas- skills applies to a given task, and web developers often apply wrong web conventions (div, localStorage, DOM APIs) that break on mobile. This Skill acts as the entry-point hub that detects the Expo stack and routes every task to the right specialized skill. ## Core Features & Use Cases - Stack Detection: Identifies an Expo project via app.json, app.config.ts, the expo dependency in package.json, or an app/ directory. - Decision Tree: Maps tasks (UI components, navigation, animations, data fetching, EAS builds, store submission, OTA updates) to the correct skill such as expo-router, expo-ui, expo-animation, or eas-app-stores. - RN vs Web Convention Table: Translates web patterns (div, a href, localStorage, button) into React Native equivalents (View, Link from expo-router, expo-secure-store, Pressable). - Component Selection Rule: Enforces checking @expo/ui first for sheets, pickers, sliders, toggles, and menus before falling back to community libraries. - Use Case: You start a session in a mobile repo and ask how to add a bottom sheet; the hub detects the Expo stack and directs you to expo-ui with the correct BottomSheet props (isPresented/onDismiss) instead of @gorhom/bottom-sheet. ## Quick Start Ask the assistant to use the expo-overview skill to determine which Expo skill fits your current mobile development task.

Frequently Asked Questions about expo-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know which Expo skill to use for my task?▼

Use the decision tree in expo-overview: it maps each task type to a skill, for example expo-router for navigation, expo-animation for gestures, expo-data-fetching for React Query, and eas-app-stores for store submission. Start at the hub, then delegate to the specific skill.

What is the difference between expo-* and eas-* skills?▼

Skills prefixed expo-* cover the open-source Expo framework (UI, routing, modules, upgrades), while eas-* skills cover the paid EAS cloud services such as builds, store submission, hosting, workflows, and OTA update insights.

Should I use @expo/ui or @gorhom/bottom-sheet for a bottom sheet?▼

Check @expo/ui first: its BottomSheet renders native SwiftUI or Jetpack Compose and is controlled via isPresented and onDismiss props. Only fall back to @gorhom/bottom-sheet or other community libraries when @expo/ui lacks the component.

How do web development patterns translate to React Native?▼

Web elements map to React Native equivalents: div becomes View, text goes inside Text, a href becomes Link from expo-router, localStorage becomes expo-secure-store or AsyncStorage, and button becomes Pressable. There is no DOM, window, or document on mobile.

Can I use Tailwind CSS classes in an Expo project?▼

Yes, through NativeWind v5, which provides className support with Tailwind v4 syntax plus React Native style props. Setup details are handled by the expo-tailwind-setup skill referenced from the hub.

When should I not use the List component from @expo/ui?▼

List from @expo/ui is not virtualized; it renders native grouped rows suited for settings screens. For large or unknown-size lists like feeds or search results, use FlatList or FlashList instead.