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 the generated auth code works against the installed SDK instead of relying on outdated examples. ## 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, forgot-password, and email-link flows with 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 Expo Router protected routes, biometrics, passkeys, and push notification registration. - Use Case: A developer asks to add phone SMS auth to an Expo app; the Skill first checks the factor is enabled in the Clerk Dashboard, then generates sign-up and sign-in screens using signUp.verifications.sendPhoneCode and signIn.phoneCode.verifyCode with a captcha mount point. ## Quick Start Ask the assistant to add Clerk authentication to your Expo app and it will set up the provider, token cache, and a working sign-in flow.
