What problem does it solve? Adding authentication to Expo and React Native apps involves many failure-prone details: token persistence, dashboard configuration, deprecated APIs, and build-type constraints. This Skill guides the implementation of Clerk auth with verified, current patterns for @clerk/expo v3.4+. ## Core Features & Use Cases - Prebuilt native components: Set up AuthView, UserButton, and UserProfileView from @clerk/expo/native for development builds, with theming via the config plugin. - Custom auth flows: Build email/password, SMS/phone OTP, MFA/TOTP, forgot-password, and combined sign-in-or-up flows using the current method-based useSignIn/useSignUp API. - Social and native sign-in: Implement browser SSO with useSSO or fully native Google/Apple sign-in hooks, plus protected routes with Expo Router guards, biometrics, passkeys, and push notifications. - Use Case: A developer asks to add phone SMS auth to an Expo app; the Skill verifies the factor is enabled in the Clerk Dashboard, then generates sign-up and sign-in screens using signUp.verifications.sendPhoneCode and signIn.phoneCode.sendCode with finalize() on completion. ## Quick Start Add Clerk authentication to my Expo app with a sign-in screen and persistent sessions across restarts.