port-bridgelisted
Install: claude install-skill robinhserrano/flutter-rn-bridge
# port-bridge — Flutter ⇄ React Native reimplementation
This skill helps you **read source in one framework and reimplement it idiomatically in the
other**. It is NOT a transpiler. Do not translate syntax token-by-token. Understand what the
source does, then write the equivalent the way a native engineer in the target framework would.
RN grounding assumes the modern Expo stack (Expo Router, Zustand, TanStack Query,
react-hook-form + zod, MMKV/expo-secure-store, TypeScript). Flutter grounding assumes VGV
conventions (GoRouter, Bloc/Cubit or Riverpod, repository layer, layered packages).
## The 5-step workflow
1. **Detect direction** — decide source and target (rules below). State it explicitly.
2. **Analyze** — read the source and understand it before writing anything: the UI tree, state,
side-effects, data flow, navigation, and external dependencies. For a whole feature, read its
collaborators too. Do not skip this to jump to code.
3. **Map** — for each concern in the source, look up the idiomatic target equivalent in the
relevant reference file (index below). Load only the files you need.
4. **Reimplement** — write clean, idiomatic target code. Where no 1:1 mapping exists or a human
must decide (a native-only plugin, an ambiguous state pattern, a platform channel), leave a
`// PORT-TODO: <what and why>` marker instead of guessing.
5. **Verify** — typecheck/lint the output in its own toolchain (`tsc --noEmit` / `expo lint` on
the RN side, `dart analyze`