Max Gorriaran

Use whenever awaited work can later change React state, navigation, storage, a backend, notifications, analytics, media, routes, provider output, or background state. Harden effects against stale, replaced, cancelled, unmounted, replayed, partially failed, or recovered operations without taking over the surrounding domain policy.

Use for Expo SDK and native-platform engineering involving dependency compatibility, app config or config plugins, permissions, development-build boundaries, TaskManager or background work, notifications, updates and runtime channels, native ownership, or iOS, Android, and New Architecture behavior. Exclude ordinary React Native UI, release execution, and session or location policy unless the task crosses an Expo platform seam.

Use when selecting, running, or reporting verification for React Native and Expo changes, especially navigation, async state, location, background behavior, notifications, accessibility, native configuration, release readiness, simulator or device QA, screenshots, video, and evidence reports. Keep structural validation, startup discovery, instruction-following, hosted behavior, simulator behavior, physical-device behavior, and release proof distinct.

Use when mobile work changes app navigation or geographic route transitions, including stacks, tabs, navigator-presented modals, links, auth callbacks, back behavior, resets, route preview or guidance, arrival, rerouting, destination identity, geometry currentness, map-camera ownership, external maps, or navigation recovery. Exclude component-only modals and bottom sheets unless they also change a navigation transition.

Use for mobile session and location policy involving startup or hydration; start, pause, resume, end, replacement, cleanup, orphan handling, or restart recovery; session ownership; foreground or background transitions; GPS permission, accuracy, stale or unavailable fixes; geofences, notifications, and pocket or locked-phone behavior. Exclude presentation-only work, route-transition policy, and Expo registration or native configuration unless those boundaries also change.

Use for ordinary React Native components, hooks, local or shared client state, accessibility, layout, lists, images, component-level modals or bottom sheets, gestures, keyboards, and measured performance work. Exclude navigator-presented routes, visual design selection, Expo or native configuration, navigation-state authority, session or location policy, and release work unless the task crosses those boundaries.