Expo
Stack Pack.

Expo coverage from the lens of shipping production mobile apps: Expo Router for navigation, EAS Build + EAS Update for delivery, the New Architecture (Fabric + TurboModules) on by default, Hermes as the engine, dev clients for native modules. Opinions on Expo Router vs React Navigation, OTA updates vs full re-submits, and when to eject.

Why it's in the catalog. React Native's New Architecture finally rolled out as default in 2025. The pack carries the migration patterns, the Expo Router opinions, and the EAS workflows that ship apps without devops overhead.

Headline products and features the pack carries opinions on. Each lives as its own canonical page under stacks/expo/<product>.md in the etyb-skills repo — currency-stamped, sourced, opinionated.

• Expo Router
• EAS Build
• EAS Update (OTA)
• New Architecture (Fabric + TurboModules)
• Hermes
• Expo Modules
• Expo Notifications
• Dev clients
• expo-router/use
• Expo DOM components

When /etyb routes a request to one of these roles AND the Expo pack is in play, the role's reference is composed with the platform-flavored knowledge from this stack. Same role, sharper answer.

• › mobile-architect
• › frontend-architect
• › devops-engineer
• › qa-engineer

The three things on Expo that a 2024-cutoff model is most likely to get wrong — and that this pack reflects.

• New Architecture default: Fabric + TurboModules now baseline; legacy bridge officially deprecated
• Expo Router 4: file-based routing with native tabs and typed routes
• EAS Update: per-channel OTA without re-submission for JS-only changes

The Expo pack comes with /etyb — one install, every pack ready to go. The overlay loads automatically when the work calls for it.

$ npx skills add e-t-y-b/etyb-skills

See the full install guide for Claude Code plugin and manual routes.