Skip to content

lukedj78/dev-flow / rn-expo-router

rn-expo-router

Verified

Use when working with navigation in an Expo + React Native app: adding routes, building tab/stack/drawer layouts, modal routes, dynamic segments (e.g. /profile/[id]), typed routes, deep linking, search params. Triggers on: "add a route", "wire up tabs", "open as modal", "set up deep linking", "configure navigation", or whenever an agent is about to touch a file under app/. Not for: styling navigation chrome (rn-styling), animating transitions (rn-animations-gestures, Wave 3), or non-RN web routing.

references/decision-tree.md

View on GitHub
> Sources: docs.expo.dev/router, internal opinion.

# Decision tree — Expo Router

## Q1: Stack, Tabs, or Drawer?

```
Are the top-level destinations a fixed small set the user switches between?
├── YES, 2-5 destinations    → Tabs (bottom on phones, top on web)
├── YES, 6+ destinations     → Drawer
└── NO, it's a hierarchy / flow → Stack (push/pop)
```

You can NEST them: a Stack inside a Tab, a Tab inside a Drawer, etc. The most common modern app: `Stack` at root → `(tabs)` group with `Tabs` layout → each tab has its own Stack of screens.

## Q2: Should this screen be a route or a component?

```
Does the user reach it via URL / share / deep link / push?
├── YES → file in app/ (route)
└── NO  → component in components/
```

## Q3: Modal or full screen?

```
Is the action temporary, dismissible, and shouldn't lose context?
├── YES → modal: <Stack.Screen options={{ presentation: 'modal' }} />
└── NO  → normal stack push
```

Use modal for: filters, sort, share sheet, settings overlay, sign-in prompt.
Use push for: detail view, list-to-item, anything you'd back-button out of.

## Q4: Should this protected area be a group or just a layout?

```
Multiple screens share the same auth-gate?
├── YES → (app)/ group with _layout.tsx that Redirects if no user
└── NO  → check auth inline in the single screen
```

## Q5: Where do I put the bottom-tab icons?

```
In the parent _layout.tsx, on each <Tabs.Screen options={{ tabBarIcon: () => ... }} />.
NEVER in the screen file itself.
```
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall