[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-expo-eas-update":3,"mdc--tux6dt-key":34,"related-repo-expo-eas-update":978,"related-org-expo-eas-update":1078},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"eas-update","configure EAS Update for Expo apps","EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview\u002Fstaging\u002Fproduction channels, explaining branches\u002Fchannels\u002Fruntime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"expo","Expo","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fexpo.png",[12,14,17,20],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"JavaScript","javascript",{"name":18,"slug":19,"type":13},"Mobile","mobile",{"name":21,"slug":22,"type":13},"Deployment","deployment",2494,"https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills","2026-09-04T08:00:30.477765","MIT",140,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"A collection of AI agent skills for working with Expo projects and Expo Application Services","https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002FHEAD\u002Fplugins\u002Fexpo\u002Fskills\u002Feas-update","---\nname: eas-update\ndescription: \"EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview\u002Fstaging\u002Fproduction channels, explaining branches\u002Fchannels\u002Fruntime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.\"\nversion: 1.0.0\nlicense: MIT\nallowed-tools: \"Bash(npx expo *), Bash(npx *eas-cli@*), Bash(eas *)\"\n---\n\n# EAS Update\n\n> **EAS service - costs apply.** EAS Update is available on the Free plan; publishing and delivery use update, bandwidth, and storage allowances, with higher limits on paid plans. See https:\u002F\u002Fexpo.dev\u002Fpricing.\n\nUse EAS Update to deliver compatible JavaScript, styling, and asset changes to installed apps without submitting a new native binary. Native-code changes still require a new build.\n\n## Start with the supported configuration path\n\nBefore changing anything, inspect `package.json`, the Expo app config, `eas.json` if present, and whether `ios\u002F` or `android\u002F` are tracked. Use what you find when reviewing the CLI's changes:\n\n- Preserve existing dynamic or platform-specific app configuration.\n- If `eas.json` exists, preserve its profiles and existing channel assignments. The CLI adds a channel matching the profile name only to build profiles that do not already have one.\n- If `eas.json` is absent, do not create it by hand. The CLI may direct the user to run `eas build:configure` separately.\n- With tracked native projects, expect the CLI to synchronize the platform's native Update configuration. Without them, expect Continuous Native Generation to apply the native configuration during a later build.\n\nDetect the Expo SDK version before installing packages or interpreting version-specific behavior.\n\nIf `expo-updates` is not installed, install the SDK-compatible version:\n\n```bash\nnpx expo install expo-updates\n```\n\nConfigure from the project root:\n\n```bash\nnpx eas-cli@latest update:configure\n```\n\nUse `eas update:configure` rather than manually inventing `updates.url`, `runtimeVersion`, native metadata, or build-profile channels. The command understands EAS project linking, Continuous Native Generation, and projects with committed native directories. Review and explain its resulting diff.\n\nIf the command cannot proceed because the project is not linked or the user has not authorized the required remote operation, stop after any independently valid package installation and explain what remains. Do not partially reproduce `update:configure` by adding a runtime-version policy, config plugin, update URL, or channels by hand.\n\nFor dynamic app config, non-EAS builds, or a command that cannot complete automatically, follow the current setup documentation instead of guessing: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fgetting-started.md.\n\n## Keep the model straight\n\n- **Build:** the installed native app. It contains native code, an embedded update, a platform, a runtime version, and normally a channel fixed at build time.\n- **Update:** a published JavaScript bundle, assets, and metadata for one platform and runtime version.\n- **Branch:** an ordered stream of updates. Its newest compatible update is active.\n- **Channel:** a stable deployment target embedded in builds. On the server, it points to a branch.\n- **Runtime version:** the compatibility boundary between an update and the native code in a build.\n\nA build receives an update only when platform and runtime version match and the build's channel points to the branch containing that update:\n\n```text\ninstalled build (channel: production, runtime: 1.1.1, platform: ios)\n  -> production channel\n  -> production branch\n  -> newest update for runtime 1.1.1 and ios\n```\n\nChannels and branches commonly have the same name, but they are separate objects. `eas channel:edit` changes a channel's server-side branch mapping for every build on that channel. It does not change an individual installation's embedded channel.\n\nUse this model to make decisions, but explain only the concepts needed for the user's request rather than reciting the entire model every time.\n\n## Decide whether an update is compatible\n\nUse an update for changes to JavaScript, styling, and bundled assets that the installed native runtime already supports.\n\nCreate a new native build when a change adds or modifies native code or native configuration, including most native-library additions and SDK upgrades. Do not work around a runtime mismatch or imply that publishing can add native capabilities to an existing build. See https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fruntime-versions.md.\n\nDo not change the project's runtime-version policy as an incidental fix. Explain how the current policy affects compatibility; treat changing it as a separate decision because it changes which installed builds can receive future updates.\n\n## Publish deliberately\n\nCheck the current CLI help before relying on remembered flags:\n\n```bash\nnpx eas-cli@latest update --help\n```\n\nFor the common channel-based flow:\n\n```bash\nnpx eas-cli@latest update \\\n  --channel \u003Cchannel> \\\n  --message \"\u003Cmessage>\" \\\n  --environment \u003Cenvironment>\n```\n\nSDK 55 and later require an EAS environment for publishing. Choose the environment intentionally so exported code receives the intended variables.\n\nPublishing changes remote state and can affect installed applications. Before running it, establish the exact project, channel, environment, platforms, runtime version, and message. Publish to production only when the user has explicitly requested or approved it; if the authorization or target is ambiguous, stop before the command and ask. Do not infer a production destination solely from the current Git branch.\n\nPrefer a preview or staging channel for validation. When promoting a tested update, use the documented deployment flow so production receives the same artifact where possible: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fdeployment.md.\n\n## Test according to the build type\n\n### Development builds\n\nPreview updates with the development build's Extensions UI, the EAS dashboard, or Expo Orbit. A normal `expo-dev-client` development build does not behave like a release build's automatic startup update flow.\n\n### Preview, TestFlight, and production builds\n\nRelease builds normally prioritize startup speed. With the default launch behavior, the app may start its current embedded or cached update while downloading a newly published update in the background. The downloaded update is applied on a later restart.\n\nFor manual QA, fully terminate the app rather than backgrounding it, reopen it, allow the update time to download, and, if the change is not visible, fully terminate and reopen it once more. Describe this as **up to two cold launches**, not a TestFlight-specific ritual:\n\n1. One launch can discover and download the update.\n2. The following launch can run the downloaded update.\n\nDo not automatically change `fallbackToCacheTimeout` to avoid the second launch. Waiting at startup trades launch latency and reliability for faster update activation. If the app needs an intentional update UX, consider the `expo-updates` APIs for checking, fetching, and presenting a non-blocking restart action. Use the `expo-updates` API reference for the project's detected SDK version.\n\n## Debug a build that did not update\n\nCheck these in order:\n\n1. Confirm the update was published to the intended EAS project, channel or branch, platform, and environment.\n2. Compare the installed build's platform and runtime version with the published update.\n3. Confirm the build actually contains the expected update URL and channel; app-config changes take effect only in a newly compiled build.\n4. Inspect the channel-to-branch mapping and the active update on that branch.\n5. Fully terminate the release build and allow for the normal download-then-apply lifecycle.\n6. Use the current debugging guide for native logs, export problems, and configuration checks: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fdebug.md.\n\nNever bypass a compatibility or anti-bricking safeguard merely to make an update appear.\n\n## Advanced and adjacent workflows\n\n- **Channel surfing:** an individual release build can override its `expo-channel-name` request header to request another compatible channel. This differs from changing the server-side channel-to-branch mapping. Follow https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fchannel-surfing.md and preserve its access-control, persistence, recovery, and compatibility constraints.\n- **Update health:** load `eas-update-insights` for adoption, launch failures, crash rate, payload size, and rollout monitoring after publishing.\n- **Store releases:** load `eas-app-stores` when native changes require a new TestFlight, App Store, or Play Store build.\n\n## Official references\n\n- Setup: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fgetting-started.md\n- Concepts and matching: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fhow-it-works.md\n- Deployment: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fdeployment.md\n- Debugging: https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fdebug.md\n- Current EAS CLI reference: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fcli.md\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"eas-update\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n",{"data":35,"body":38},{"name":4,"description":6,"version":36,"license":26,"allowed-tools":37},"1.0.0","Bash(npx expo *), Bash(npx *eas-cli@*), Bash(eas *)",{"type":39,"children":40},"root",[41,49,75,80,87,125,171,176,188,227,232,256,285,298,310,316,369,374,384,397,402,408,413,425,430,436,441,469,474,592,597,602,614,620,627,640,646,651,663,677,704,710,715,755,760,766,830,836,891,897,902,967,972],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","EAS Update",{"type":42,"tag":50,"props":51,"children":52},"blockquote",{},[53],{"type":42,"tag":54,"props":55,"children":56},"p",{},[57,63,65,73],{"type":42,"tag":58,"props":59,"children":60},"strong",{},[61],{"type":47,"value":62},"EAS service - costs apply.",{"type":47,"value":64}," EAS Update is available on the Free plan; publishing and delivery use update, bandwidth, and storage allowances, with higher limits on paid plans. See ",{"type":42,"tag":66,"props":67,"children":71},"a",{"href":68,"rel":69},"https:\u002F\u002Fexpo.dev\u002Fpricing",[70],"nofollow",[72],{"type":47,"value":68},{"type":47,"value":74},".",{"type":42,"tag":54,"props":76,"children":77},{},[78],{"type":47,"value":79},"Use EAS Update to deliver compatible JavaScript, styling, and asset changes to installed apps without submitting a new native binary. Native-code changes still require a new build.",{"type":42,"tag":81,"props":82,"children":84},"h2",{"id":83},"start-with-the-supported-configuration-path",[85],{"type":47,"value":86},"Start with the supported configuration path",{"type":42,"tag":54,"props":88,"children":89},{},[90,92,99,101,107,109,115,117,123],{"type":47,"value":91},"Before changing anything, inspect ",{"type":42,"tag":93,"props":94,"children":96},"code",{"className":95},[],[97],{"type":47,"value":98},"package.json",{"type":47,"value":100},", the Expo app config, ",{"type":42,"tag":93,"props":102,"children":104},{"className":103},[],[105],{"type":47,"value":106},"eas.json",{"type":47,"value":108}," if present, and whether ",{"type":42,"tag":93,"props":110,"children":112},{"className":111},[],[113],{"type":47,"value":114},"ios\u002F",{"type":47,"value":116}," or ",{"type":42,"tag":93,"props":118,"children":120},{"className":119},[],[121],{"type":47,"value":122},"android\u002F",{"type":47,"value":124}," are tracked. Use what you find when reviewing the CLI's changes:",{"type":42,"tag":126,"props":127,"children":128},"ul",{},[129,135,147,166],{"type":42,"tag":130,"props":131,"children":132},"li",{},[133],{"type":47,"value":134},"Preserve existing dynamic or platform-specific app configuration.",{"type":42,"tag":130,"props":136,"children":137},{},[138,140,145],{"type":47,"value":139},"If ",{"type":42,"tag":93,"props":141,"children":143},{"className":142},[],[144],{"type":47,"value":106},{"type":47,"value":146}," exists, preserve its profiles and existing channel assignments. The CLI adds a channel matching the profile name only to build profiles that do not already have one.",{"type":42,"tag":130,"props":148,"children":149},{},[150,151,156,158,164],{"type":47,"value":139},{"type":42,"tag":93,"props":152,"children":154},{"className":153},[],[155],{"type":47,"value":106},{"type":47,"value":157}," is absent, do not create it by hand. The CLI may direct the user to run ",{"type":42,"tag":93,"props":159,"children":161},{"className":160},[],[162],{"type":47,"value":163},"eas build:configure",{"type":47,"value":165}," separately.",{"type":42,"tag":130,"props":167,"children":168},{},[169],{"type":47,"value":170},"With tracked native projects, expect the CLI to synchronize the platform's native Update configuration. Without them, expect Continuous Native Generation to apply the native configuration during a later build.",{"type":42,"tag":54,"props":172,"children":173},{},[174],{"type":47,"value":175},"Detect the Expo SDK version before installing packages or interpreting version-specific behavior.",{"type":42,"tag":54,"props":177,"children":178},{},[179,180,186],{"type":47,"value":139},{"type":42,"tag":93,"props":181,"children":183},{"className":182},[],[184],{"type":47,"value":185},"expo-updates",{"type":47,"value":187}," is not installed, install the SDK-compatible version:",{"type":42,"tag":189,"props":190,"children":195},"pre",{"className":191,"code":192,"language":193,"meta":194,"style":194},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","npx expo install expo-updates\n","bash","",[196],{"type":42,"tag":93,"props":197,"children":198},{"__ignoreMap":194},[199],{"type":42,"tag":200,"props":201,"children":204},"span",{"class":202,"line":203},"line",1,[205,211,217,222],{"type":42,"tag":200,"props":206,"children":208},{"style":207},"--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B",[209],{"type":47,"value":210},"npx",{"type":42,"tag":200,"props":212,"children":214},{"style":213},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[215],{"type":47,"value":216}," expo",{"type":42,"tag":200,"props":218,"children":219},{"style":213},[220],{"type":47,"value":221}," install",{"type":42,"tag":200,"props":223,"children":224},{"style":213},[225],{"type":47,"value":226}," expo-updates\n",{"type":42,"tag":54,"props":228,"children":229},{},[230],{"type":47,"value":231},"Configure from the project root:",{"type":42,"tag":189,"props":233,"children":235},{"className":191,"code":234,"language":193,"meta":194,"style":194},"npx eas-cli@latest update:configure\n",[236],{"type":42,"tag":93,"props":237,"children":238},{"__ignoreMap":194},[239],{"type":42,"tag":200,"props":240,"children":241},{"class":202,"line":203},[242,246,251],{"type":42,"tag":200,"props":243,"children":244},{"style":207},[245],{"type":47,"value":210},{"type":42,"tag":200,"props":247,"children":248},{"style":213},[249],{"type":47,"value":250}," eas-cli@latest",{"type":42,"tag":200,"props":252,"children":253},{"style":213},[254],{"type":47,"value":255}," update:configure\n",{"type":42,"tag":54,"props":257,"children":258},{},[259,261,267,269,275,277,283],{"type":47,"value":260},"Use ",{"type":42,"tag":93,"props":262,"children":264},{"className":263},[],[265],{"type":47,"value":266},"eas update:configure",{"type":47,"value":268}," rather than manually inventing ",{"type":42,"tag":93,"props":270,"children":272},{"className":271},[],[273],{"type":47,"value":274},"updates.url",{"type":47,"value":276},", ",{"type":42,"tag":93,"props":278,"children":280},{"className":279},[],[281],{"type":47,"value":282},"runtimeVersion",{"type":47,"value":284},", native metadata, or build-profile channels. The command understands EAS project linking, Continuous Native Generation, and projects with committed native directories. Review and explain its resulting diff.",{"type":42,"tag":54,"props":286,"children":287},{},[288,290,296],{"type":47,"value":289},"If the command cannot proceed because the project is not linked or the user has not authorized the required remote operation, stop after any independently valid package installation and explain what remains. Do not partially reproduce ",{"type":42,"tag":93,"props":291,"children":293},{"className":292},[],[294],{"type":47,"value":295},"update:configure",{"type":47,"value":297}," by adding a runtime-version policy, config plugin, update URL, or channels by hand.",{"type":42,"tag":54,"props":299,"children":300},{},[301,303,309],{"type":47,"value":302},"For dynamic app config, non-EAS builds, or a command that cannot complete automatically, follow the current setup documentation instead of guessing: ",{"type":42,"tag":66,"props":304,"children":307},{"href":305,"rel":306},"https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fgetting-started.md",[70],[308],{"type":47,"value":305},{"type":47,"value":74},{"type":42,"tag":81,"props":311,"children":313},{"id":312},"keep-the-model-straight",[314],{"type":47,"value":315},"Keep the model straight",{"type":42,"tag":126,"props":317,"children":318},{},[319,329,339,349,359],{"type":42,"tag":130,"props":320,"children":321},{},[322,327],{"type":42,"tag":58,"props":323,"children":324},{},[325],{"type":47,"value":326},"Build:",{"type":47,"value":328}," the installed native app. It contains native code, an embedded update, a platform, a runtime version, and normally a channel fixed at build time.",{"type":42,"tag":130,"props":330,"children":331},{},[332,337],{"type":42,"tag":58,"props":333,"children":334},{},[335],{"type":47,"value":336},"Update:",{"type":47,"value":338}," a published JavaScript bundle, assets, and metadata for one platform and runtime version.",{"type":42,"tag":130,"props":340,"children":341},{},[342,347],{"type":42,"tag":58,"props":343,"children":344},{},[345],{"type":47,"value":346},"Branch:",{"type":47,"value":348}," an ordered stream of updates. Its newest compatible update is active.",{"type":42,"tag":130,"props":350,"children":351},{},[352,357],{"type":42,"tag":58,"props":353,"children":354},{},[355],{"type":47,"value":356},"Channel:",{"type":47,"value":358}," a stable deployment target embedded in builds. On the server, it points to a branch.",{"type":42,"tag":130,"props":360,"children":361},{},[362,367],{"type":42,"tag":58,"props":363,"children":364},{},[365],{"type":47,"value":366},"Runtime version:",{"type":47,"value":368}," the compatibility boundary between an update and the native code in a build.",{"type":42,"tag":54,"props":370,"children":371},{},[372],{"type":47,"value":373},"A build receives an update only when platform and runtime version match and the build's channel points to the branch containing that update:",{"type":42,"tag":189,"props":375,"children":379},{"className":376,"code":378,"language":47,"meta":194},[377],"language-text","installed build (channel: production, runtime: 1.1.1, platform: ios)\n  -> production channel\n  -> production branch\n  -> newest update for runtime 1.1.1 and ios\n",[380],{"type":42,"tag":93,"props":381,"children":382},{"__ignoreMap":194},[383],{"type":47,"value":378},{"type":42,"tag":54,"props":385,"children":386},{},[387,389,395],{"type":47,"value":388},"Channels and branches commonly have the same name, but they are separate objects. ",{"type":42,"tag":93,"props":390,"children":392},{"className":391},[],[393],{"type":47,"value":394},"eas channel:edit",{"type":47,"value":396}," changes a channel's server-side branch mapping for every build on that channel. It does not change an individual installation's embedded channel.",{"type":42,"tag":54,"props":398,"children":399},{},[400],{"type":47,"value":401},"Use this model to make decisions, but explain only the concepts needed for the user's request rather than reciting the entire model every time.",{"type":42,"tag":81,"props":403,"children":405},{"id":404},"decide-whether-an-update-is-compatible",[406],{"type":47,"value":407},"Decide whether an update is compatible",{"type":42,"tag":54,"props":409,"children":410},{},[411],{"type":47,"value":412},"Use an update for changes to JavaScript, styling, and bundled assets that the installed native runtime already supports.",{"type":42,"tag":54,"props":414,"children":415},{},[416,418,424],{"type":47,"value":417},"Create a new native build when a change adds or modifies native code or native configuration, including most native-library additions and SDK upgrades. Do not work around a runtime mismatch or imply that publishing can add native capabilities to an existing build. See ",{"type":42,"tag":66,"props":419,"children":422},{"href":420,"rel":421},"https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fruntime-versions.md",[70],[423],{"type":47,"value":420},{"type":47,"value":74},{"type":42,"tag":54,"props":426,"children":427},{},[428],{"type":47,"value":429},"Do not change the project's runtime-version policy as an incidental fix. Explain how the current policy affects compatibility; treat changing it as a separate decision because it changes which installed builds can receive future updates.",{"type":42,"tag":81,"props":431,"children":433},{"id":432},"publish-deliberately",[434],{"type":47,"value":435},"Publish deliberately",{"type":42,"tag":54,"props":437,"children":438},{},[439],{"type":47,"value":440},"Check the current CLI help before relying on remembered flags:",{"type":42,"tag":189,"props":442,"children":444},{"className":191,"code":443,"language":193,"meta":194,"style":194},"npx eas-cli@latest update --help\n",[445],{"type":42,"tag":93,"props":446,"children":447},{"__ignoreMap":194},[448],{"type":42,"tag":200,"props":449,"children":450},{"class":202,"line":203},[451,455,459,464],{"type":42,"tag":200,"props":452,"children":453},{"style":207},[454],{"type":47,"value":210},{"type":42,"tag":200,"props":456,"children":457},{"style":213},[458],{"type":47,"value":250},{"type":42,"tag":200,"props":460,"children":461},{"style":213},[462],{"type":47,"value":463}," update",{"type":42,"tag":200,"props":465,"children":466},{"style":213},[467],{"type":47,"value":468}," --help\n",{"type":42,"tag":54,"props":470,"children":471},{},[472],{"type":47,"value":473},"For the common channel-based flow:",{"type":42,"tag":189,"props":475,"children":477},{"className":191,"code":476,"language":193,"meta":194,"style":194},"npx eas-cli@latest update \\\n  --channel \u003Cchannel> \\\n  --message \"\u003Cmessage>\" \\\n  --environment \u003Cenvironment>\n",[478],{"type":42,"tag":93,"props":479,"children":480},{"__ignoreMap":194},[481,502,536,564],{"type":42,"tag":200,"props":482,"children":483},{"class":202,"line":203},[484,488,492,496],{"type":42,"tag":200,"props":485,"children":486},{"style":207},[487],{"type":47,"value":210},{"type":42,"tag":200,"props":489,"children":490},{"style":213},[491],{"type":47,"value":250},{"type":42,"tag":200,"props":493,"children":494},{"style":213},[495],{"type":47,"value":463},{"type":42,"tag":200,"props":497,"children":499},{"style":498},"--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8",[500],{"type":47,"value":501}," \\\n",{"type":42,"tag":200,"props":503,"children":505},{"class":202,"line":504},2,[506,511,517,522,527,532],{"type":42,"tag":200,"props":507,"children":508},{"style":213},[509],{"type":47,"value":510},"  --channel",{"type":42,"tag":200,"props":512,"children":514},{"style":513},"--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF",[515],{"type":47,"value":516}," \u003C",{"type":42,"tag":200,"props":518,"children":519},{"style":213},[520],{"type":47,"value":521},"channe",{"type":42,"tag":200,"props":523,"children":524},{"style":498},[525],{"type":47,"value":526},"l",{"type":42,"tag":200,"props":528,"children":529},{"style":513},[530],{"type":47,"value":531},">",{"type":42,"tag":200,"props":533,"children":534},{"style":498},[535],{"type":47,"value":501},{"type":42,"tag":200,"props":537,"children":539},{"class":202,"line":538},3,[540,545,550,555,560],{"type":42,"tag":200,"props":541,"children":542},{"style":213},[543],{"type":47,"value":544},"  --message",{"type":42,"tag":200,"props":546,"children":547},{"style":513},[548],{"type":47,"value":549}," \"",{"type":42,"tag":200,"props":551,"children":552},{"style":213},[553],{"type":47,"value":554},"\u003Cmessage>",{"type":42,"tag":200,"props":556,"children":557},{"style":513},[558],{"type":47,"value":559},"\"",{"type":42,"tag":200,"props":561,"children":562},{"style":498},[563],{"type":47,"value":501},{"type":42,"tag":200,"props":565,"children":567},{"class":202,"line":566},4,[568,573,577,582,587],{"type":42,"tag":200,"props":569,"children":570},{"style":213},[571],{"type":47,"value":572},"  --environment",{"type":42,"tag":200,"props":574,"children":575},{"style":513},[576],{"type":47,"value":516},{"type":42,"tag":200,"props":578,"children":579},{"style":213},[580],{"type":47,"value":581},"environmen",{"type":42,"tag":200,"props":583,"children":584},{"style":498},[585],{"type":47,"value":586},"t",{"type":42,"tag":200,"props":588,"children":589},{"style":513},[590],{"type":47,"value":591},">\n",{"type":42,"tag":54,"props":593,"children":594},{},[595],{"type":47,"value":596},"SDK 55 and later require an EAS environment for publishing. Choose the environment intentionally so exported code receives the intended variables.",{"type":42,"tag":54,"props":598,"children":599},{},[600],{"type":47,"value":601},"Publishing changes remote state and can affect installed applications. Before running it, establish the exact project, channel, environment, platforms, runtime version, and message. Publish to production only when the user has explicitly requested or approved it; if the authorization or target is ambiguous, stop before the command and ask. Do not infer a production destination solely from the current Git branch.",{"type":42,"tag":54,"props":603,"children":604},{},[605,607,613],{"type":47,"value":606},"Prefer a preview or staging channel for validation. When promoting a tested update, use the documented deployment flow so production receives the same artifact where possible: ",{"type":42,"tag":66,"props":608,"children":611},{"href":609,"rel":610},"https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fdeployment.md",[70],[612],{"type":47,"value":609},{"type":47,"value":74},{"type":42,"tag":81,"props":615,"children":617},{"id":616},"test-according-to-the-build-type",[618],{"type":47,"value":619},"Test according to the build type",{"type":42,"tag":621,"props":622,"children":624},"h3",{"id":623},"development-builds",[625],{"type":47,"value":626},"Development builds",{"type":42,"tag":54,"props":628,"children":629},{},[630,632,638],{"type":47,"value":631},"Preview updates with the development build's Extensions UI, the EAS dashboard, or Expo Orbit. A normal ",{"type":42,"tag":93,"props":633,"children":635},{"className":634},[],[636],{"type":47,"value":637},"expo-dev-client",{"type":47,"value":639}," development build does not behave like a release build's automatic startup update flow.",{"type":42,"tag":621,"props":641,"children":643},{"id":642},"preview-testflight-and-production-builds",[644],{"type":47,"value":645},"Preview, TestFlight, and production builds",{"type":42,"tag":54,"props":647,"children":648},{},[649],{"type":47,"value":650},"Release builds normally prioritize startup speed. With the default launch behavior, the app may start its current embedded or cached update while downloading a newly published update in the background. The downloaded update is applied on a later restart.",{"type":42,"tag":54,"props":652,"children":653},{},[654,656,661],{"type":47,"value":655},"For manual QA, fully terminate the app rather than backgrounding it, reopen it, allow the update time to download, and, if the change is not visible, fully terminate and reopen it once more. Describe this as ",{"type":42,"tag":58,"props":657,"children":658},{},[659],{"type":47,"value":660},"up to two cold launches",{"type":47,"value":662},", not a TestFlight-specific ritual:",{"type":42,"tag":664,"props":665,"children":666},"ol",{},[667,672],{"type":42,"tag":130,"props":668,"children":669},{},[670],{"type":47,"value":671},"One launch can discover and download the update.",{"type":42,"tag":130,"props":673,"children":674},{},[675],{"type":47,"value":676},"The following launch can run the downloaded update.",{"type":42,"tag":54,"props":678,"children":679},{},[680,682,688,690,695,697,702],{"type":47,"value":681},"Do not automatically change ",{"type":42,"tag":93,"props":683,"children":685},{"className":684},[],[686],{"type":47,"value":687},"fallbackToCacheTimeout",{"type":47,"value":689}," to avoid the second launch. Waiting at startup trades launch latency and reliability for faster update activation. If the app needs an intentional update UX, consider the ",{"type":42,"tag":93,"props":691,"children":693},{"className":692},[],[694],{"type":47,"value":185},{"type":47,"value":696}," APIs for checking, fetching, and presenting a non-blocking restart action. Use the ",{"type":42,"tag":93,"props":698,"children":700},{"className":699},[],[701],{"type":47,"value":185},{"type":47,"value":703}," API reference for the project's detected SDK version.",{"type":42,"tag":81,"props":705,"children":707},{"id":706},"debug-a-build-that-did-not-update",[708],{"type":47,"value":709},"Debug a build that did not update",{"type":42,"tag":54,"props":711,"children":712},{},[713],{"type":47,"value":714},"Check these in order:",{"type":42,"tag":664,"props":716,"children":717},{},[718,723,728,733,738,743],{"type":42,"tag":130,"props":719,"children":720},{},[721],{"type":47,"value":722},"Confirm the update was published to the intended EAS project, channel or branch, platform, and environment.",{"type":42,"tag":130,"props":724,"children":725},{},[726],{"type":47,"value":727},"Compare the installed build's platform and runtime version with the published update.",{"type":42,"tag":130,"props":729,"children":730},{},[731],{"type":47,"value":732},"Confirm the build actually contains the expected update URL and channel; app-config changes take effect only in a newly compiled build.",{"type":42,"tag":130,"props":734,"children":735},{},[736],{"type":47,"value":737},"Inspect the channel-to-branch mapping and the active update on that branch.",{"type":42,"tag":130,"props":739,"children":740},{},[741],{"type":47,"value":742},"Fully terminate the release build and allow for the normal download-then-apply lifecycle.",{"type":42,"tag":130,"props":744,"children":745},{},[746,748,754],{"type":47,"value":747},"Use the current debugging guide for native logs, export problems, and configuration checks: ",{"type":42,"tag":66,"props":749,"children":752},{"href":750,"rel":751},"https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fdebug.md",[70],[753],{"type":47,"value":750},{"type":47,"value":74},{"type":42,"tag":54,"props":756,"children":757},{},[758],{"type":47,"value":759},"Never bypass a compatibility or anti-bricking safeguard merely to make an update appear.",{"type":42,"tag":81,"props":761,"children":763},{"id":762},"advanced-and-adjacent-workflows",[764],{"type":47,"value":765},"Advanced and adjacent workflows",{"type":42,"tag":126,"props":767,"children":768},{},[769,795,813],{"type":42,"tag":130,"props":770,"children":771},{},[772,777,779,785,787,793],{"type":42,"tag":58,"props":773,"children":774},{},[775],{"type":47,"value":776},"Channel surfing:",{"type":47,"value":778}," an individual release build can override its ",{"type":42,"tag":93,"props":780,"children":782},{"className":781},[],[783],{"type":47,"value":784},"expo-channel-name",{"type":47,"value":786}," request header to request another compatible channel. This differs from changing the server-side channel-to-branch mapping. Follow ",{"type":42,"tag":66,"props":788,"children":791},{"href":789,"rel":790},"https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fchannel-surfing.md",[70],[792],{"type":47,"value":789},{"type":47,"value":794}," and preserve its access-control, persistence, recovery, and compatibility constraints.",{"type":42,"tag":130,"props":796,"children":797},{},[798,803,805,811],{"type":42,"tag":58,"props":799,"children":800},{},[801],{"type":47,"value":802},"Update health:",{"type":47,"value":804}," load ",{"type":42,"tag":93,"props":806,"children":808},{"className":807},[],[809],{"type":47,"value":810},"eas-update-insights",{"type":47,"value":812}," for adoption, launch failures, crash rate, payload size, and rollout monitoring after publishing.",{"type":42,"tag":130,"props":814,"children":815},{},[816,821,822,828],{"type":42,"tag":58,"props":817,"children":818},{},[819],{"type":47,"value":820},"Store releases:",{"type":47,"value":804},{"type":42,"tag":93,"props":823,"children":825},{"className":824},[],[826],{"type":47,"value":827},"eas-app-stores",{"type":47,"value":829}," when native changes require a new TestFlight, App Store, or Play Store build.",{"type":42,"tag":81,"props":831,"children":833},{"id":832},"official-references",[834],{"type":47,"value":835},"Official references",{"type":42,"tag":126,"props":837,"children":838},{},[839,849,860,870,880],{"type":42,"tag":130,"props":840,"children":841},{},[842,844],{"type":47,"value":843},"Setup: ",{"type":42,"tag":66,"props":845,"children":847},{"href":305,"rel":846},[70],[848],{"type":47,"value":305},{"type":42,"tag":130,"props":850,"children":851},{},[852,854],{"type":47,"value":853},"Concepts and matching: ",{"type":42,"tag":66,"props":855,"children":858},{"href":856,"rel":857},"https:\u002F\u002Fdocs.expo.dev\u002Feas-update\u002Fhow-it-works.md",[70],[859],{"type":47,"value":856},{"type":42,"tag":130,"props":861,"children":862},{},[863,865],{"type":47,"value":864},"Deployment: ",{"type":42,"tag":66,"props":866,"children":868},{"href":609,"rel":867},[70],[869],{"type":47,"value":609},{"type":42,"tag":130,"props":871,"children":872},{},[873,875],{"type":47,"value":874},"Debugging: ",{"type":42,"tag":66,"props":876,"children":878},{"href":750,"rel":877},[70],[879],{"type":47,"value":750},{"type":42,"tag":130,"props":881,"children":882},{},[883,885],{"type":47,"value":884},"Current EAS CLI reference: ",{"type":42,"tag":66,"props":886,"children":889},{"href":887,"rel":888},"https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fcli.md",[70],[890],{"type":47,"value":887},{"type":42,"tag":81,"props":892,"children":894},{"id":893},"submitting-feedback",[895],{"type":47,"value":896},"Submitting Feedback",{"type":42,"tag":54,"props":898,"children":899},{},[900],{"type":47,"value":901},"If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:",{"type":42,"tag":189,"props":903,"children":905},{"className":191,"code":904,"language":193,"meta":194,"style":194},"npx --yes submit-expo-feedback@latest --category skills --subject \"eas-update\" \"\u003Cactionable feedback>\"\n",[906],{"type":42,"tag":93,"props":907,"children":908},{"__ignoreMap":194},[909],{"type":42,"tag":200,"props":910,"children":911},{"class":202,"line":203},[912,916,921,926,931,936,941,945,949,953,957,962],{"type":42,"tag":200,"props":913,"children":914},{"style":207},[915],{"type":47,"value":210},{"type":42,"tag":200,"props":917,"children":918},{"style":213},[919],{"type":47,"value":920}," --yes",{"type":42,"tag":200,"props":922,"children":923},{"style":213},[924],{"type":47,"value":925}," submit-expo-feedback@latest",{"type":42,"tag":200,"props":927,"children":928},{"style":213},[929],{"type":47,"value":930}," --category",{"type":42,"tag":200,"props":932,"children":933},{"style":213},[934],{"type":47,"value":935}," skills",{"type":42,"tag":200,"props":937,"children":938},{"style":213},[939],{"type":47,"value":940}," --subject",{"type":42,"tag":200,"props":942,"children":943},{"style":513},[944],{"type":47,"value":549},{"type":42,"tag":200,"props":946,"children":947},{"style":213},[948],{"type":47,"value":4},{"type":42,"tag":200,"props":950,"children":951},{"style":513},[952],{"type":47,"value":559},{"type":42,"tag":200,"props":954,"children":955},{"style":513},[956],{"type":47,"value":549},{"type":42,"tag":200,"props":958,"children":959},{"style":213},[960],{"type":47,"value":961},"\u003Cactionable feedback>",{"type":42,"tag":200,"props":963,"children":964},{"style":513},[965],{"type":47,"value":966},"\"\n",{"type":42,"tag":54,"props":968,"children":969},{},[970],{"type":47,"value":971},"Only submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.",{"type":42,"tag":973,"props":974,"children":975},"style",{},[976],{"type":47,"value":977},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":979,"total":1077},[980,995,1010,1025,1039,1046,1059],{"slug":827,"name":827,"fn":981,"description":982,"org":983,"tags":984,"stars":23,"repoUrl":24,"updatedAt":994},"deploy and submit Expo apps to stores","EAS service (paid). Deploy Expo apps to the app stores with EAS - build and submit to the iOS App Store, Google Play Store, and TestFlight, configure eas.json build and submit profiles, manage app versions and build numbers, and publish App Store metadata and ASO. Use whenever the user wants to deploy, release, or ship an app to production or the app stores, is preparing a production build, running eas build or eas submit, shipping to TestFlight, bumping version or build numbers, or setting up store listing metadata. For deploying an Expo website or API routes, use the eas-hosting skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[985,988,989,990,993],{"name":986,"slug":987,"type":13},"Android","android",{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":991,"slug":992,"type":13},"iOS","ios",{"name":18,"slug":19,"type":13},"2026-08-06T05:38:27.496958",{"slug":996,"name":996,"fn":997,"description":998,"org":999,"tags":1000,"stars":23,"repoUrl":24,"updatedAt":1009},"eas-hosting","deploy Expo websites to EAS Hosting","EAS service (paid). Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods, request handling, CORS). Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains. Not for native builds or store releases - use the eas-app-stores skill for those.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1001,1002,1003,1006],{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":1004,"slug":1005,"type":13},"Frontend","frontend",{"name":1007,"slug":1008,"type":13},"Web Development","web-development","2026-08-06T05:38:23.520822",{"slug":1011,"name":1011,"fn":1012,"description":1013,"org":1014,"tags":1015,"stars":23,"repoUrl":24,"updatedAt":1024},"eas-observe","configure EAS Observe for Expo apps","EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot\u002FObserveRoot HOC, markInteractive and ObserveInteractiveMarker, the useObserve hook, the Expo Router \u002F React Navigation integrations for per-route metrics, user-defined events via `Observe.logEvent`, error reporting via ObserveErrorBoundary and `Observe.reportError`, and runtime config such as sampleRate and dispatchInDebug), querying via the EAS CLI (`eas observe:metrics-summary`, `observe:metrics`, `observe:routes`, `observe:events`, `observe:session`, `observe:versions`), interpreting the resulting metrics (cold\u002Fwarm launch, TTR, TTI, navigation cold\u002Fwarm TTR, update download, and the TTI frameRate\u002Fdevice\u002Fnetwork params for triaging slow startups), or shipping an Observe integration inside a third-party package.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1016,1017,1018,1021],{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":1019,"slug":1020,"type":13},"Observability","observability",{"name":1022,"slug":1023,"type":13},"React Native","react-native","2026-08-16T03:31:47.802249",{"slug":1026,"name":1026,"fn":1027,"description":1028,"org":1029,"tags":1030,"stars":23,"repoUrl":24,"updatedAt":1038},"eas-simulator","run and control remote iOS and Android simulators","EAS service (paid). Run and control a user's app on a remote iOS\u002FAndroid simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run\u002Finstall\u002Fscreenshot my app', 'I'm on Linux\u002FCursor and need an iOS device', 'no sim on this box \u002F headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud\u002Fremote\u002Fshareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build\u002FUpdate, web preview, or physical devices.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1031,1032,1035,1036,1037],{"name":986,"slug":987,"type":13},{"name":1033,"slug":1034,"type":13},"CLI","cli",{"name":9,"slug":8,"type":13},{"name":991,"slug":992,"type":13},{"name":18,"slug":19,"type":13},"2026-08-06T05:38:35.510759",{"slug":4,"name":4,"fn":5,"description":6,"org":1040,"tags":1041,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1042,1043,1044,1045],{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":15,"slug":16,"type":13},{"name":18,"slug":19,"type":13},{"slug":810,"name":810,"fn":1047,"description":1048,"org":1049,"tags":1050,"stars":23,"repoUrl":24,"updatedAt":1058},"check health of EAS Updates","EAS service (paid). Check the health of published EAS Update: crash rates, install\u002Flaunch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1051,1054,1055,1056,1057],{"name":1052,"slug":1053,"type":13},"Analytics","analytics",{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":1019,"slug":1020,"type":13},"2026-08-06T05:38:33.530661",{"slug":1060,"name":1060,"fn":1061,"description":1062,"org":1063,"tags":1064,"stars":23,"repoUrl":24,"updatedAt":1076},"eas-workflows","configure EAS workflows for Expo projects","EAS service (paid). Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\u002FCD or workflows in an Expo or EAS context, mentions .eas\u002Fworkflows\u002F, or wants help with EAS build pipelines or deployment automation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1065,1068,1071,1072,1073],{"name":1066,"slug":1067,"type":13},"Automation","automation",{"name":1069,"slug":1070,"type":13},"CI\u002FCD","ci-cd",{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":1074,"slug":1075,"type":13},"YAML","yaml","2026-08-16T03:31:46.821054",25,{"items":1079,"total":1206},[1080,1088,1095,1102,1110,1117,1125,1133,1147,1158,1173,1191],{"slug":827,"name":827,"fn":981,"description":982,"org":1081,"tags":1082,"stars":23,"repoUrl":24,"updatedAt":994},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1083,1084,1085,1086,1087],{"name":986,"slug":987,"type":13},{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":991,"slug":992,"type":13},{"name":18,"slug":19,"type":13},{"slug":996,"name":996,"fn":997,"description":998,"org":1089,"tags":1090,"stars":23,"repoUrl":24,"updatedAt":1009},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1091,1092,1093,1094],{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":1004,"slug":1005,"type":13},{"name":1007,"slug":1008,"type":13},{"slug":1011,"name":1011,"fn":1012,"description":1013,"org":1096,"tags":1097,"stars":23,"repoUrl":24,"updatedAt":1024},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1098,1099,1100,1101],{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":1019,"slug":1020,"type":13},{"name":1022,"slug":1023,"type":13},{"slug":1026,"name":1026,"fn":1027,"description":1028,"org":1103,"tags":1104,"stars":23,"repoUrl":24,"updatedAt":1038},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1105,1106,1107,1108,1109],{"name":986,"slug":987,"type":13},{"name":1033,"slug":1034,"type":13},{"name":9,"slug":8,"type":13},{"name":991,"slug":992,"type":13},{"name":18,"slug":19,"type":13},{"slug":4,"name":4,"fn":5,"description":6,"org":1111,"tags":1112,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1113,1114,1115,1116],{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":15,"slug":16,"type":13},{"name":18,"slug":19,"type":13},{"slug":810,"name":810,"fn":1047,"description":1048,"org":1118,"tags":1119,"stars":23,"repoUrl":24,"updatedAt":1058},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1120,1121,1122,1123,1124],{"name":1052,"slug":1053,"type":13},{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":1019,"slug":1020,"type":13},{"slug":1060,"name":1060,"fn":1061,"description":1062,"org":1126,"tags":1127,"stars":23,"repoUrl":24,"updatedAt":1076},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1128,1129,1130,1131,1132],{"name":1066,"slug":1067,"type":13},{"name":1069,"slug":1070,"type":13},{"name":21,"slug":22,"type":13},{"name":9,"slug":8,"type":13},{"name":1074,"slug":1075,"type":13},{"slug":1134,"name":1134,"fn":1135,"description":1136,"org":1137,"tags":1138,"stars":23,"repoUrl":24,"updatedAt":1146},"expo-animation","build animations in React Native and Expo","Framework (OSS). Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use `animate`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1139,1142,1143,1144,1145],{"name":1140,"slug":1141,"type":13},"Animation","animation",{"name":9,"slug":8,"type":13},{"name":1004,"slug":1005,"type":13},{"name":18,"slug":19,"type":13},{"name":1022,"slug":1023,"type":13},"2026-08-19T03:58:54.679247",{"slug":1148,"name":1148,"fn":1149,"description":1150,"org":1151,"tags":1152,"stars":23,"repoUrl":24,"updatedAt":1157},"expo-app-clip","add iOS App Clip targets to Expo","Framework (OSS). Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1153,1154,1155,1156],{"name":9,"slug":8,"type":13},{"name":991,"slug":992,"type":13},{"name":18,"slug":19,"type":13},{"name":1022,"slug":1023,"type":13},"2026-08-06T05:38:29.493721",{"slug":1159,"name":1159,"fn":1160,"description":1161,"org":1162,"tags":1163,"stars":23,"repoUrl":24,"updatedAt":1172},"expo-brownfield","integrate Expo and React Native into native apps","Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR\u002FXCFramework, or adding Expo to an existing Kotlin\u002FSwift project. Covers both the isolated approach and the integrated approach.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1164,1165,1166,1169,1170,1171],{"name":986,"slug":987,"type":13},{"name":9,"slug":8,"type":13},{"name":1167,"slug":1168,"type":13},"Integrations","integrations",{"name":991,"slug":992,"type":13},{"name":18,"slug":19,"type":13},{"name":1022,"slug":1023,"type":13},"2026-08-06T05:38:22.505099",{"slug":1174,"name":1174,"fn":1175,"description":1176,"org":1177,"tags":1178,"stars":23,"repoUrl":24,"updatedAt":1190},"expo-data-fetching","fetch and manage data in Expo apps","Framework (OSS). Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1179,1182,1185,1186,1187],{"name":1180,"slug":1181,"type":13},"API Development","api-development",{"name":1183,"slug":1184,"type":13},"Caching","caching",{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":1188,"slug":1189,"type":13},"React","react","2026-08-06T05:38:25.502479",{"slug":1192,"name":1192,"fn":1193,"description":1194,"org":1195,"tags":1196,"stars":23,"repoUrl":24,"updatedAt":1205},"expo-design-system","build design systems for Expo apps","Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant\u002Fsize\u002Fstate prop conventions, and rules for when to extract a repeated view into a shared component. Use when creating or organizing theme files and design tokens (theme.ts \u002F theme\u002F), extending an existing theme or styling library (NativeWind, Tamagui, Restyle, Unistyles) in its own idiom, standardizing styles so screens (including AI-generated ones) look consistent and polished, building an in-app component library, or auditing an app for design-system drift (hardcoded colors, spacing, fonts). For platform styling specifics (semantic colors, HIG rules, native controls) use expo-native-ui; for folder layout of a new app use expo-project-structure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1197,1200,1201,1202],{"name":1198,"slug":1199,"type":13},"Design System","design-system",{"name":9,"slug":8,"type":13},{"name":1022,"slug":1023,"type":13},{"name":1203,"slug":1204,"type":13},"UI Components","ui-components","2026-09-01T08:00:07.345681",27]