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/decision-tree.md
View on GitHub> Sources: docs.expo.dev/workflow/overview, docs.expo.dev/development-builds, https://expo.dev/changelog/expo-go-and-app-store-may-2026, https://expo.dev/go, internal opinion.
# Decision tree — fundamentals
## Q1: Expo managed or bare?
```
Need a native library Expo cannot wrap?
├── NO → MANAGED. Always start here.
└── YES → Check expo-modules registry first. Still NO?
├── Library is a one-off (e.g. legacy SDK) → BARE
└── Library is broadly useful → write a config plugin instead, stay MANAGED
```
**Default: managed. 95% of apps stay here.**
## Q2: Expo Go or dev client?
```
Do you need the app on a physical iPhone?
├── YES → DEV BUILD (expo-dev-client). No store Expo Go loads SDK 58 yet (2026-10-17).
└── NO → Android device, or iOS simulator? Expo Go is still fine for a quick spin.
Adding a custom native module / config plugin / custom build flag?
└── YES → DEV BUILD anyway.
```
**Default for a brand-new app: a development build (`expo-dev-client`).**
This flipped in 2026. Through SDK 57 the App Store build of Expo Go was **frozen at SDK 54** — SDK 55, 56 and 57 were never approved by App Review. We now ship **SDK 58**, and per the SDK 58 changelog (2026-10-15) *the new Expo Go "will be released on the App Store and Google Play within a few weeks"* and **will support only SDK 58**. Until it lands, no store Expo Go — iOS **or Android** — opens our project, and `npx create-expo-app` still scaffolds SDK 57 (use `--template default@sdk-58`). Whether App Review actually approves the iOS build is `[VERIFY]`.
What still works:
- **Android** — the Play Store build tracks current SDKs, but the SDK 58 one is not out yet (2026-10-17); until then, a dev build.
- **iOS simulator** — current-SDK Expo Go is installed by Expo CLI (or from https://expo.dev/go), bypassing App Review entirely. `[VERIFY]` for SDK 58 before the store release: the changelog says to start SDK 58 projects on a dev build.
- **iOS physical device** — you need either a dev build, or `eas go` (builds *your own* copy of Expo Go and delivers it via TestFlight; requires a paid Apple Developer membership).
Expo now positions Expo Go as an educational tool for beginners' first steps and recommends development builds for real work. Treat Expo Go as a demo convenience, not the team's daily driver: one `eas build --profile development` per native change buys you a client that matches the app you actually ship.
## Q3: New Architecture ON or OFF?
```
ON, unless: a critical library is still incompatible (very rare in 2026).
```
If you turn it OFF: write the reason in `app.json` as a comment-equivalent (a `// reason` in README) and add a TODO to flip ON later.
## Q4: TypeScript strict mode?
```
ALWAYS strict: true in tsconfig.json. extends "expo/tsconfig.base".
```
## Q5: Monorepo?
Out of scope for Wave 1. If asked, defer with: "single-package Expo app for now; if you need a monorepo, that's a separate setup (pnpm workspaces or bun workspaces) outside this skill set."
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 |