Skip to content

lukedj78/dev-flow / rn-fundamentals

rn-fundamentals

Verified

Use 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).

FileKindSize
SKILL.mdskill md5.6 KB
references/.gitkeepother0 B
references/concepts.mdmarkdown2.5 KB
references/decision-tree.mdmarkdown3.0 KB
references/patterns.mdmarkdown2.2 KB
references/stack-defaults.mdmarkdown6.0 KB
references/zustand-rn.mdmarkdown9.4 KB

references/patterns.md

View on GitHub
> Sources: reactnative.dev best practices, docs.expo.dev, codewithbeto.dev lessons 5-6 (free).

# Patterns and anti-patterns at the foundational level

## Project layout (mandatory)

```
my-app/
├── app/                  # Expo Router file-based routes
│   ├── _layout.tsx
│   └── index.tsx
├── components/           # presentational + reusable components
├── lib/                  # framework-agnostic helpers (api client, supabase, utils)
├── store/                # Zustand stores
├── types/                # shared TS types
├── assets/               # images, fonts
├── tailwind.config.js
├── global.css            # NativeWind v4 entry CSS
├── app.json
├── tsconfig.json
└── package.json
```

## DO

- ✅ Use `Pressable` for new touchable components.
- ✅ Wrap every root screen in `SafeAreaView` (from `react-native-safe-area-context`).
- ✅ Use `expo-image` for static and remote images (gives caching and placeholders).
- ✅ Use `@shopify/flash-list` for any list with > 20 items or unknown length.
- ✅ Use TypeScript paths (e.g. `@/components/Button`) configured in `tsconfig.json`.
- ✅ Read env vars only via `process.env.EXPO_PUBLIC_*` (public) or expo-constants (build-time secrets).

## DON'T

- ❌ Use `TouchableOpacity` / `TouchableHighlight` in new code — `Pressable` covers all cases.
- ❌ Hardcode magic numbers — pull from `tailwind.config.js` tokens.
- ❌ Use `Image` from `react-native` — use `expo-image`.
- ❌ Use `FlatList` for long lists — use `FlashList`.
- ❌ Use `react-navigation` directly — Expo Router wraps it.
- ❌ Use `console.log` in shipped code — guard dev-only logging with `if (__DEV__)`, which the production bundle strips.
- ❌ Use `dimensions = Dimensions.get('window')` at module top-level — recompute on `useWindowDimensions` to handle rotation/foldables.

## When the rules clash with the course (codewithbeto)

The course teaches `TouchableOpacity`, `Image`, `FlatList`, and `StyleSheet` in the free lessons because they are simpler for beginners. In this skill set, **prefer the modern alternative** (`Pressable`, `expo-image`, `FlashList`, NativeWind). The course concepts still apply 1:1.
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