mobile-expo-safety

Enforces Expo dependency, Metro config, and build-check rules for React Native development.

3|1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/nghyane/VSTEP --skill mobile-expo-safety-nghyane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-expo-safety
Source: https://github.com/nghyane/VSTEP/tree/main/apps/mobile-v2/.agents/skills/mobile-expo-safety
Command: npx skills add https://github.com/nghyane/VSTEP --skill mobile-expo-safety-nghyane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expo projects break easily when developers install incompatible packages, misconfigure Metro or Babel, or skip type and lint checks, leading to cryptic build errors and wasted debugging time. ## Core Features & Use Cases - Dependency Safety Rules: Mandates npx expo install over bun add and requires checking Expo SDK ~54 compatibility before adding any package. - Config Guardrails: Restricts edits to metro.config.js and babel.config.js to specific justified cases with backup and testing requirements. - Troubleshooting Playbooks: Provides fixes for common failures like "Unable to resolve module", native module linking errors, hot reload issues, and stale TypeScript caches. - Use Case: Before adding expo-secure-store to a React Native app, load this Skill to verify SDK compatibility, install it correctly, and run the mandatory typecheck and lint gates afterward. ## Quick Start Load the Expo safety rules before adding any dependency or editing Metro or Babel config in the mobile app.

Frequently Asked Questions about mobile-expo-safety

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

FAQPage Schema
How do I add a package to an Expo project correctly?▼

Use npx expo install package-name instead of bun add or npm install so the version auto-resolves to match your Expo SDK. If the package has native code, rebuild the app afterward with npx expo run:android or run:ios.

How to fix "Unable to resolve module" in Expo?▼

This error usually comes from installing with bun add instead of npx expo install, a stale Metro cache, or a wrong import path. Run npx expo install --fix, delete node_modules/.cache, and restart with npx expo start -c.

Does Expo Go support all native modules?▼

No, Expo Go does not support all native modules. Check the Expo docs for a built-in alternative first; otherwise run npx expo prebuild to generate native projects and test with npx expo run:android or run:ios on a real build.

Why does my Expo build fail after adding a package?▼

Build failures typically come from a version conflict with the Expo SDK, an incompatible native dependency, or missing permissions in app.json. Verify the package version matches SDK ~54, check app.json permissions, and run npx expo doctor.

When should I edit metro.config.js or babel.config.js in Expo?▼

Only edit metro.config.js to add a resolver for a new file type or fix module resolution, and only add Babel plugins after verifying Expo SDK compatibility. Back up the file first, comment the reason, and test the build immediately.