lukedj78/dev-flow / rn-fundamentals
rn-fundamentals
VerifiedUse at the start of any React Native or Expo task to lock in foundational choices: Expo managed workflow as default, latest Expo SDK with New Architecture ON, TypeScript, npm. Triggers on: "starting a new RN/Expo project", "what is the right architecture for an Expo app", "managed vs bare workflow", questions about Fabric/Hermes/JSI/New Architecture, "differences between RN and React web". Also triggers as a precondition when any other rn-* skill is selected and project setup is unclear. Not for: styling (rn-styling), navigation (rn-expo-router), data (rn-data-fetching).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.6 KB |
| references/.gitkeep | other | 0 B |
| references/concepts.md | markdown | 2.5 KB |
| references/decision-tree.md | markdown | 3.0 KB |
| references/patterns.md | markdown | 2.2 KB |
| references/stack-defaults.md | markdown | 6.0 KB |
| references/zustand-rn.md | markdown | 9.4 KB |
references/concepts.md
View on GitHub> Sources: reactnative.dev/architecture, docs.expo.dev/get-started, codewithbeto.dev lessons 1-3 (free).
# Concepts — React Native + Expo
## RN vs React on the web (one-line each)
- **DOM**: there is none. JSX maps to native views (`<View>` → `UIView` on iOS / `android.view.View` on Android), not to `<div>`.
- **Styling**: no CSS cascade. Styles are JS objects (via `StyleSheet`, NativeWind, or inline). Layout is **Flexbox by default, in column direction** (web is row).
- **Events**: `onPress`, not `onClick`. `Pressable` is the modern primitive (NOT `TouchableOpacity` for new code).
- **Routing**: no `<a href>`. Use Expo Router (file-based, see `rn-expo-router`).
- **Persistence**: no `localStorage`. Use `AsyncStorage` or `expo-secure-store`.
## The bridge, JSI, Fabric, Hermes (what to actually know)
- **Old Architecture**: JS thread talks to native via a serialized "bridge". Async only, batching, sometimes laggy.
- **JSI (JavaScript Interface)**: replaces the bridge with direct C++ binding. Synchronous calls become possible.
- **Fabric**: the new UI renderer built on JSI. Concurrent rendering capable.
- **TurboModules**: native modules over JSI. Lazy-loaded.
- **Hermes**: the JS engine optimized for RN (smaller bundle, faster start). Default since SDK 49.
- **New Architecture = Fabric + TurboModules + Hermes**. Nothing to enable: since **SDK 55 it is always on and cannot be disabled**, and `newArchEnabled` is ignored (it is not even in `@expo/config-types@58.0.3`'s schema, checked 2026-10-17).
## Managed vs bare (TL;DR)
- **Managed**: `app.json` describes the native config; you don't touch Xcode/Android Studio. Expo prebuild generates native code on demand. 95% of apps.
- **Bare**: you own `ios/` and `android/` folders. Use when you need a native library Expo cannot wrap (rare).
- **Expo Go**: dev sandbox for managed apps with no custom native deps. Quick to start, can't load custom native modules. ⚠️ We ship **SDK 58**; the store Expo Go that supports it (SDK 58 only) is announced for the App Store and Google Play "within a few weeks" of 2026-10-15 — until then no store build opens our project (the App Store one was frozen at SDK 54 through SDK 57). Use a dev build. See `decision-tree.md` Q2.
- **Dev client** (`expo-dev-client`): custom Expo Go for your app, supports any native module. **This is the default** — start here rather than reaching for Expo Go.
## Sources
- https://reactnative.dev/architecture/landing-page
- https://docs.expo.dev/workflow/overview/
- https://docs.expo.dev/develop/development-builds/introduction/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |