What problem does it solve? Adding authentication to an Expo or React Native app involves many failure-prone details: token persistence, dashboard configuration, deprecated APIs, and build-type constraints. This Skill provides verified, current patterns for @clerk/expo so auth works correctly on the first build. ## 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 native Google/Apple sign-in hooks, plus protected routes with Expo Router guards, biometrics, passkeys, and push notification registration. - Use Case: A developer asks to add phone SMS auth to their Expo app; the Skill first verifies SMS is enabled in the Clerk Dashboard, then generates sign-up and sign-in flows with sendPhoneCode/verifyPhoneCode, finalize(), and the required captcha mount point. ## Quick Start Add Clerk authentication to my Expo app with a sign-in screen and persistent sessions across restarts.