expo

Build, route, deploy, and maintain Expo SDK 55 mobile apps with EAS.

15|2|Updated May 23, 2026
One-click install
npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill expo-vkirill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo
Source: https://github.com/VKirill/antigravity-for-claude-code/tree/main/skills/expo
Command: npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill expo-vkirill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the friction of building, configuring, routing, shipping, and updating iOS/Android applications with Expo SDK 55 and React Native 0.85, including the New Architecture defaults and managed native customizations.

Core Features & Use Cases

  • Expo Router navigation & typed routes: Set up Stack/Tabs/Drawer routing, dynamic segments, redirects, modals, and typed route params for safer screen-to-screen flows.
  • EAS lifecycle (Build, Update, Submit): Create eas.json profiles, publish JS-only OTA updates with correct runtimeVersion fingerprinting and channels, and submit finished binaries to App Store / Google Play.
  • Native customization, permissions, and push notifications: Implement config plugins and Expo Modules API changes at prebuild time, follow declare-then-request permission flows, and wire expo-notifications end-to-end with device token handling.

Quick Start

Ask: “Set up an Expo Router app using Expo SDK 55 with typed routes, configure EAS Build profiles for development/preview/production, and explain how to publish a fingerprinted OTA update to the production channel.”

Frequently Asked Questions about expo

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

FAQPage Schema
How do I set up Expo Router with typed routes and dynamic segments in SDK 55?

EAS Update uses fingerprint runtime version safety to ensure OTA compatibility. You publish JS-only updates to specific channels while the fingerprint policy guarantees the update matches the target binary's native code version.

How do I configure EAS Build profiles for development, preview, and production?

You configure EAS Build by creating distinct eas.json profiles for development, preview, and production environments. These profiles define build settings for iOS and Android binaries before submission to App Store and Google Play.

Can I manage native iOS and Android changes without ejecting in Expo SDK 55?

Yes, you can manage native customizations at prebuild time using config plugins and the Expo Modules API. This allows you to wire permissions, deep links, and push notifications without detaching from the managed workflow.

What is the correct flow for setting up expo-notifications push notifications end-to-end?

Setting up expo-notifications requires wiring device token handling and following a declare-then-request permission flow. You implement config plugins at prebuild time to enable push notification capabilities across iOS and Android.

How does EAS Submit work for publishing Expo apps to App Store and Google Play?

EAS Submit automates sending finished iOS and Android binaries to App Store and Google Play. After building with EAS Build profiles, you submit binaries directly through the CLI without manual native store configuration.