Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When a user needs to upgrade their Expo SDK version or fix dependency issues after an upgrade (e.g., breaking changes, deprecated packages, native build errors).
npx expo install, npx expo-doctor, prebuild) for upgrade and diagnosticsA cleanly upgraded Expo project with fixed dependencies, updated native code, and removed deprecated packages — ready to build and ship.
Use Cases
A developer is on Expo SDK 53 and wants to move to SDK 55 to use new architecture and native tabs. They invoke the skill, follow the step-by-step upgrade (npx expo install --fix, expo-doctor, prebuild if needed), and apply the native-tabs and React 19 reference migrations. The skill helps them avoid broken imports and deprecated packages, delivering a smooth upgrade with verified navigation and media features.
After upgrading, a team finds expo-av still used and build fails on audio. They use the skill's deprecated package table and expo-av-to-audio reference to migrate to expo-audio with useAudioPlayer. The skill's housekeeping steps also remove unneeded babel/metro configs. Value: clear migration path, no guesswork, and a maintainable project aligned with latest SDK norms.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File