[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A50857HSEB9AY9CCFSBDC0":3,"skill-same:01M7A50857HSEB9AY9CCFSBDC0":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7A50857HSEB9AY9CCFSBDC0","clerk-expo",null,"Add Clerk authentication to Expo and React Native apps using @clerk\u002Fexpo. Use for Expo setup, prebuilt native components (AuthView, UserButton), custom sign-in\u002Fsign-up flows (email, password, SMS\u002Fphone OTP, MFA), OAuth\u002FSSO, native Google\u002FApple sign-in, Expo Router protected routes, biometrics, and push notifications. Do not use for native Swift\u002FiOS, native Android\u002FKotlin, or web-only framework projects.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"MIT","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Add Clerk authentication to Expo and React Native apps using @clerk\u002Fexpo. Use for Expo setup, prebuilt native components (AuthView, UserButton), custom sign-in\u002Fsign-up flows (email, password, SMS\u002Fphone OTP, MFA), OAuth\u002FSSO, native Google\u002FApple sign-in, Expo Router protected routes, biometrics, and push notifications. Do not use for native Swift\u002FiOS, native Android\u002FKotlin, or web-only framework projects.\"\nlicense: \"MIT\"\nmetadata: {\"author\":\"clerk\",\"version\":\"2.0.0\"}\n---\n# Clerk Expo (React Native)\n\nImplement Clerk in Expo \u002F React Native projects. This skill inlines verified patterns for the stable surface (provider, token cache, flows) and requires source inspection of the installed `@clerk\u002Fexpo` package for anything volatile (component props, hook signatures).\n\n## Activation Rules\n\nActivate when either is true:\n- The user asks for auth in an Expo or React Native app, or mentions `@clerk\u002Fexpo`, `ClerkProvider`, Expo Router auth, or Clerk hooks in a native app.\n- The project is Expo\u002FReact Native (`app.json` \u002F `app.config.js`, `expo` in `package.json`, `metro.config.js`, `@clerk\u002Fexpo` dependency).\n\nRoute away when:\n- Native iOS\u002FSwift project (`.xcodeproj`, `Package.swift`) → `clerk-swift`\n- Native Android\u002FKotlin project (`build.gradle` without React Native) → `clerk-android`\n- Web-only framework (Next.js, Remix, plain React, etc.) → the matching framework skill\n\n## Intent Map\n\nMatch what the user asked for, then load the reference(s) listed. Load only what the task needs.\n\n| User intent (examples) | Path | Reference |\n|------------------------|------|-----------|\n| \"Add auth to my app\" \u002F \"add sign-in with Clerk\" | Prebuilt native components (default) | references\u002Fsetup.md + references\u002Fprebuilt-components.md |\n| \"Add auth\" but Expo Go \u002F web \u002F custom UI required | Custom flows | references\u002Fsetup.md + references\u002Fcustom-flows.md |\n| \"Add phone \u002F SMS auth\", \"email OTP\", \"passwordless\" | Custom flow, `phoneCode` \u002F `emailCode` | references\u002Fcustom-flows.md |\n| \"Sign in with Google\u002FApple\u002FGitHub\", \"social login\", \"SSO\" | Browser SSO or native buttons | references\u002Fsso-and-native-auth.md |\n| \"MFA \u002F 2FA \u002F TOTP\", \"forgot password\", \"email link\" | Custom flow additions | references\u002Fcustom-flows.md |\n| \"Protect routes\u002Fscreens\", \"redirect if signed out\" | Expo Router guards | references\u002Fprotected-routes.md |\n| \"Show user profile\", \"org switching\", \"push notifications\", \"sign out\", \"call my backend\" | App recipes | references\u002Frecipes.md |\n| \"Biometric login\", \"Face ID\", \"passkeys\" | Device features | references\u002Frecipes.md |\n\n## Default Path Decision\n\nWhen the user says \"add auth\" without specifying UI:\n\n1. **Default to prebuilt native components** (`AuthView` + `UserButton` from `@clerk\u002Fexpo\u002Fnative`). Fastest to working auth; UI is maintained by Clerk. Tell the developer they are in beta and require a development build.\n2. **Fall back to custom flows** when any of these hold — say why when you switch:\n   - The project must run in Expo Go (no dev build).\n   - The app targets web (native components don't render on web).\n   - The developer wants their own UI or a specific brand experience beyond theming.\n3. If the developer has an existing auth UI, extend what's there — don't rip out custom flows to insert `AuthView` (or vice versa) without being asked.\n\nDo not blend prebuilt components and custom flows for the same auth step (e.g. `AuthView` plus a custom password form). Blending is allowed only when the developer explicitly asks.\n\n## Quick Workflow\n\n1. Confirm project type (Expo\u002FRN) and pick the path per the Intent Map \u002F Default Path rules.\n2. Follow references\u002Fsetup.md: install, env key, provider, token cache, config plugin, build type.\n3. Verify dashboard prerequisites (Gate 2 and Gate 3 below).\n4. Implement from the selected reference only.\n5. Verify by building, not just by writing:\n   - Run the project's typecheck (`npx tsc --noEmit` or equivalent).\n   - Build and launch: `npx expo run:ios` \u002F `run:android` for native features, `npx expo start` for Expo Go flows. If the build fails, fix and rebuild iteratively — build errors against the installed SDK are the ground truth when this skill and the SDK disagree. After ~5 failed fix attempts, stop and ask the developer how to proceed instead of thrashing.\n   - Walk the developer through one real sign-in, then confirm the session survives an app restart (token cache working).\n\n## Execution Gates (Do Not Skip)\n\n1. **Publishable key** — Read from `process.env.EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY` (`.env` file). Never `NEXT_PUBLIC_`, never hardcoded. If no key exists, ask the developer for one (or run `npx clerk@latest init --framework expo`, which installs the SDK and writes the env file) and wait before editing files.\n2. **Native API dashboard toggle** — Clerk's Native API must be enabled for the instance: Clerk Dashboard → **Native applications** (`https:\u002F\u002Fdashboard.clerk.com\u002F~\u002Fnative-applications`). Tell the developer to verify this during setup; it is required for any native integration.\n3. **Factor availability** — Before implementing a specific strategy (SMS, email code, social provider), confirm it's enabled for the instance. Derive the Frontend API URL from the publishable key (base64-decode the middle segment) and fetch `\u003CfrontendApiUrl>\u002Fv1\u002Fenvironment?_is_native=true`, or ask the developer to check the dashboard (**User & authentication**). SMS in particular is instance-configuration-dependent — code written for a disabled factor fails at runtime, not build time.\n4. **Current custom-flows API only** — `useSignIn()` \u002F `useSignUp()` from `@clerk\u002Fexpo` (v3.4+) return `{ signIn, errors, fetchStatus }` and use method-based flows: `signIn.password()`, `signIn.phoneCode.sendCode()`, `signIn.finalize()`. Never generate the legacy pattern: destructuring `isLoaded`\u002F`setActive` from `useSignIn()`\u002F`useSignUp()` (the current hooks don't return them), or `signIn.create()` chained with `prepareFirstFactor()`\u002F`attemptFirstFactor()` + `setActive({ session })`. That pattern lives at `@clerk\u002Fexpo\u002Flegacy` and is only for maintaining existing legacy code, never for new work. Scope notes: `isLoaded` from `useAuth()`\u002F`useUser()` is current API and required in guards; `signIn.create()` itself still exists for advanced cases — prefer the factor-specific methods.\n5. **`useSSO()`, never `useOAuth()`** — `useOAuth` is deprecated. Note the asymmetry: `startSSOFlow()` still returns `{ createdSessionId, setActive }` and requires `setActive({ session: createdSessionId })` — SSO does not use `finalize()`.\n6. **Token cache** — `tokenCache` from `@clerk\u002Fexpo\u002Ftoken-cache` on `ClerkProvider`. Never use `expo-secure-store` directly for session tokens, never AsyncStorage.\n7. **`resourceCache`, never `secureStore`** — if offline resource caching comes up, `@clerk\u002Fexpo\u002Fsecure-store` is deprecated; use `resourceCache` from `@clerk\u002Fexpo\u002Fresource-cache`.\n8. **Build-type gating** — Native components (`@clerk\u002Fexpo\u002Fnative`) and native hooks (`useSignInWithGoogle`, `useSignInWithApple`, `useLocalCredentials`) require a development build (`npx expo run:ios` \u002F `run:android`), not Expo Go, and don't exist on web. For web targets use `@clerk\u002Fexpo\u002Fweb` components or custom flows. State the build requirement before implementing a native-only feature.\n9. **Combined sign-in-or-up default** — one combined flow unless the developer asks for separate sign-in and sign-up screens.\n10. **Bot protection** — custom sign-up screens must render `\u003CView nativeID=\"clerk-captcha\" \u002F>`; Clerk's bot protection is on by default and needs this mount point.\n11. **Source verification for volatile surfaces** — before using native component props or native hook options, confirm against the installed package: `node_modules\u002F@clerk\u002Fexpo\u002Fdist\u002Fnative\u002F*.d.ts` and `package.json` `exports`. The installed version wins over this skill if they disagree.\n12. **Freshness gate** — this skill was verified against `@clerk\u002Fexpo` 3.6.x. Check the installed version (`node_modules\u002F@clerk\u002Fexpo\u002Fpackage.json`). If it is a newer minor or major, treat this skill's code snippets as suspect: re-verify against the docs URL cited next to each snippet (every reference section carries one) or the installed `.d.ts` before using them. If it is older than 3.4, the method-based custom-flows API may not exist — offer an upgrade instead of writing legacy code.\n\n## Version Notes (v3.5–v3.6, June 2026)\n\n- Minimum React Native raised to **0.75** in v3.5.0 (iOS SDK now links via SPM podspec). Peer range: `expo >=53 \u003C57`.\n- Native components matured: iOS moved to Expo Modules; native↔JS session sync is automatic and bidirectional — never call `setActive()` after native-component auth.\n- The config plugin accepts a `theme` JSON file for native component styling (see references\u002Fprebuilt-components.md).\n- Native Google sign-in will move to a separate `@clerk\u002Fexpo-google-signin` package in the next major (the `@clerk\u002Fexpo\u002Fgoogle` import keeps working in v3; a dev warning announces the migration). Don't preinstall the new package on v3.\n\n## Common Pitfalls\n\n| Level | Issue | Prevention |\n|-------|-------|------------|\n| CRITICAL | Generating legacy custom-flow code (`signIn.create` + `prepareFirstFactor` + `setActive`) | Use the current method-based API (Gate 4) |\n| CRITICAL | Using `useOAuth()` | Use `useSSO()` (Gate 5) |\n| CRITICAL | Implementing SMS\u002Fsocial auth without checking the factor is enabled | Check environment\u002Fdashboard first (Gate 3) |\n| CRITICAL | Native components targeted at Expo Go or web | Require a dev build; offer custom flows otherwise (Gate 8) |\n| CRITICAL | Sign-up screen missing `\u003CView nativeID=\"clerk-captcha\" \u002F>` | Always include it (Gate 10) |\n| HIGH | `NEXT_PUBLIC_` env prefix, or env var read inside `node_modules` | `EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY`, passed explicitly to `ClerkProvider` |\n| HIGH | Session lost on restart | `tokenCache` from `@clerk\u002Fexpo\u002Ftoken-cache` on the provider |\n| HIGH | Calling `setActive()` after `AuthView` \u002F `UserButton` auth | Native components sync sessions automatically |\n| HIGH | Pairing `AuthView` with `useSignInWithGoogle`\u002F`useSignInWithApple` | `AuthView` renders enabled social providers itself |\n| HIGH | Calling `WebBrowser.maybeCompleteAuthSession()` manually | `ClerkProvider` handles it |\n| HIGH | Splitting sign-in \u002F sign-up without being asked | Combined flow by default (Gate 9) |\n| MEDIUM | Missing `isLoaded` check before `isSignedIn` in guards | Always gate on `isLoaded` first |\n| MEDIUM | Using `yalc`\u002F`pnpm link` for local `@clerk\u002Fexpo` development | Use Verdaccio or pkg.pr.new |\n\n## See Also\n\n- `clerk` — top-level router\n- `clerk-swift` \u002F `clerk-android` — native mobile SDKs\n- `clerk-orgs`, `clerk-billing`, `clerk-webhooks` — feature skills (hooks work the same in Expo)\n- Installed package source: `node_modules\u002F@clerk\u002Fexpo\u002F`\n- https:\u002F\u002Fclerk.com\u002Fdocs\u002Fgetting-started\u002Fquickstart (Expo SDK tab)\n- https:\u002F\u002Fclerk.com\u002Fdocs\u002Freference\u002Fexpo\u002Foverview\n- https:\u002F\u002Fgithub.com\u002Fclerk\u002Fclerk-expo-quickstart — three official example apps: JS-only (Expo Go), JS + native sign-in buttons, native components\n","# Clerk Expo (React Native)\n\nImplement Clerk in Expo \u002F React Native projects. This skill inlines verified patterns for the stable surface (provider, token cache, flows) and requires source inspection of the installed `@clerk\u002Fexpo` package for anything volatile (component props, hook signatures).\n\n## Activation Rules\n\nActivate when either is true:\n- The user asks for auth in an Expo or React Native app, or mentions `@clerk\u002Fexpo`, `ClerkProvider`, Expo Router auth, or Clerk hooks in a native app.\n- The project is Expo\u002FReact Native (`app.json` \u002F `app.config.js`, `expo` in `package.json`, `metro.config.js`, `@clerk\u002Fexpo` dependency).\n\nRoute away when:\n- Native iOS\u002FSwift project (`.xcodeproj`, `Package.swift`) → `clerk-swift`\n- Native Android\u002FKotlin project (`build.gradle` without React Native) → `clerk-android`\n- Web-only framework (Next.js, Remix, plain React, etc.) → the matching framework skill\n\n## Intent Map\n\nMatch what the user asked for, then load the reference(s) listed. Load only what the task needs.\n\n| User intent (examples) | Path | Reference |\n|------------------------|------|-----------|\n| \"Add auth to my app\" \u002F \"add sign-in with Clerk\" | Prebuilt native components (default) | references\u002Fsetup.md + references\u002Fprebuilt-components.md |\n| \"Add auth\" but Expo Go \u002F web \u002F custom UI required | Custom flows | references\u002Fsetup.md + references\u002Fcustom-flows.md |\n| \"Add phone \u002F SMS auth\", \"email OTP\", \"passwordless\" | Custom flow, `phoneCode` \u002F `emailCode` | references\u002Fcustom-flows.md |\n| \"Sign in with Google\u002FApple\u002FGitHub\", \"social login\", \"SSO\" | Browser SSO or native buttons | references\u002Fsso-and-native-auth.md |\n| \"MFA \u002F 2FA \u002F TOTP\", \"forgot password\", \"email link\" | Custom flow additions | references\u002Fcustom-flows.md |\n| \"Protect routes\u002Fscreens\", \"redirect if signed out\" | Expo Router guards | references\u002Fprotected-routes.md |\n| \"Show user profile\", \"org switching\", \"push notifications\", \"sign out\", \"call my backend\" | App recipes | references\u002Frecipes.md |\n| \"Biometric login\", \"Face ID\", \"passkeys\" | Device features | references\u002Frecipes.md |\n\n## Default Path Decision\n\nWhen the user says \"add auth\" without specifying UI:\n\n1. **Default to prebuilt native components** (`AuthView` + `UserButton` from `@clerk\u002Fexpo\u002Fnative`). Fastest to working auth; UI is maintained by Clerk. Tell the developer they are in beta and require a development build.\n2. **Fall back to custom flows** when any of these hold — say why when you switch:\n   - The project must run in Expo Go (no dev build).\n   - The app targets web (native components don't render on web).\n   - The developer wants their own UI or a specific brand experience beyond theming.\n3. If the developer has an existing auth UI, extend what's there — don't rip out custom flows to insert `AuthView` (or vice versa) without being asked.\n\nDo not blend prebuilt components and custom flows for the same auth step (e.g. `AuthView` plus a custom password form). Blending is allowed only when the developer explicitly asks.\n\n## Quick Workflow\n\n1. Confirm project type (Expo\u002FRN) and pick the path per the Intent Map \u002F Default Path rules.\n2. Follow references\u002Fsetup.md: install, env key, provider, token cache, config plugin, build type.\n3. Verify dashboard prerequisites (Gate 2 and Gate 3 below).\n4. Implement from the selected reference only.\n5. Verify by building, not just by writing:\n   - Run the project's typecheck (`npx tsc --noEmit` or equivalent).\n   - Build and launch: `npx expo run:ios` \u002F `run:android` for native features, `npx expo start` for Expo Go flows. If the build fails, fix and rebuild iteratively — build errors against the installed SDK are the ground truth when this skill and the SDK disagree. After ~5 failed fix attempts, stop and ask the developer how to proceed instead of thrashing.\n   - Walk the developer through one real sign-in, then confirm the session survives an app restart (token cache working).\n\n## Execution Gates (Do Not Skip)\n\n1. **Publishable key** — Read from `process.env.EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY` (`.env` file). Never `NEXT_PUBLIC_`, never hardcoded. If no key exists, ask the developer for one (or run `npx clerk@latest init --framework expo`, which installs the SDK and writes the env file) and wait before editing files.\n2. **Native API dashboard toggle** — Clerk's Native API must be enabled for the instance: Clerk Dashboard → **Native applications** (`https:\u002F\u002Fdashboard.clerk.com\u002F~\u002Fnative-applications`). Tell the developer to verify this during setup; it is required for any native integration.\n3. **Factor availability** — Before implementing a specific strategy (SMS, email code, social provider), confirm it's enabled for the instance. Derive the Frontend API URL from the publishable key (base64-decode the middle segment) and fetch `\u003CfrontendApiUrl>\u002Fv1\u002Fenvironment?_is_native=true`, or ask the developer to check the dashboard (**User & authentication**). SMS in particular is instance-configuration-dependent — code written for a disabled factor fails at runtime, not build time.\n4. **Current custom-flows API only** — `useSignIn()` \u002F `useSignUp()` from `@clerk\u002Fexpo` (v3.4+) return `{ signIn, errors, fetchStatus }` and use method-based flows: `signIn.password()`, `signIn.phoneCode.sendCode()`, `signIn.finalize()`. Never generate the legacy pattern: destructuring `isLoaded`\u002F`setActive` from `useSignIn()`\u002F`useSignUp()` (the current hooks don't return them), or `signIn.create()` chained with `prepareFirstFactor()`\u002F`attemptFirstFactor()` + `setActive({ session })`. That pattern lives at `@clerk\u002Fexpo\u002Flegacy` and is only for maintaining existing legacy code, never for new work. Scope notes: `isLoaded` from `useAuth()`\u002F`useUser()` is current API and required in guards; `signIn.create()` itself still exists for advanced cases — prefer the factor-specific methods.\n5. **`useSSO()`, never `useOAuth()`** — `useOAuth` is deprecated. Note the asymmetry: `startSSOFlow()` still returns `{ createdSessionId, setActive }` and requires `setActive({ session: createdSessionId })` — SSO does not use `finalize()`.\n6. **Token cache** — `tokenCache` from `@clerk\u002Fexpo\u002Ftoken-cache` on `ClerkProvider`. Never use `expo-secure-store` directly for session tokens, never AsyncStorage.\n7. **`resourceCache`, never `secureStore`** — if offline resource caching comes up, `@clerk\u002Fexpo\u002Fsecure-store` is deprecated; use `resourceCache` from `@clerk\u002Fexpo\u002Fresource-cache`.\n8. **Build-type gating** — Native components (`@clerk\u002Fexpo\u002Fnative`) and native hooks (`useSignInWithGoogle`, `useSignInWithApple`, `useLocalCredentials`) require a development build (`npx expo run:ios` \u002F `run:android`), not Expo Go, and don't exist on web. For web targets use `@clerk\u002Fexpo\u002Fweb` components or custom flows. State the build requirement before implementing a native-only feature.\n9. **Combined sign-in-or-up default** — one combined flow unless the developer asks for separate sign-in and sign-up screens.\n10. **Bot protection** — custom sign-up screens must render `\u003CView nativeID=\"clerk-captcha\" \u002F>`; Clerk's bot protection is on by default and needs this mount point.\n11. **Source verification for volatile surfaces** — before using native component props or native hook options, confirm against the installed package: `node_modules\u002F@clerk\u002Fexpo\u002Fdist\u002Fnative\u002F*.d.ts` and `package.json` `exports`. The installed version wins over this skill if they disagree.\n12. **Freshness gate** — this skill was verified against `@clerk\u002Fexpo` 3.6.x. Check the installed version (`node_modules\u002F@clerk\u002Fexpo\u002Fpackage.json`). If it is a newer minor or major, treat this skill's code snippets as suspect: re-verify against the docs URL cited next to each snippet (every reference section carries one) or the installed `.d.ts` before using them. If it is older than 3.4, the method-based custom-flows API may not exist — offer an upgrade instead of writing legacy code.\n\n## Version Notes (v3.5–v3.6, June 2026)\n\n- Minimum React Native raised to **0.75** in v3.5.0 (iOS SDK now links via SPM podspec). Peer range: `expo >=53 \u003C57`.\n- Native components matured: iOS moved to Expo Modules; native↔JS session sync is automatic and bidirectional — never call `setActive()` after native-component auth.\n- The config plugin accepts a `theme` JSON file for native component styling (see references\u002Fprebuilt-components.md).\n- Native Google sign-in will move to a separate `@clerk\u002Fexpo-google-signin` package in the next major (the `@clerk\u002Fexpo\u002Fgoogle` import keeps working in v3; a dev warning announces the migration). Don't preinstall the new package on v3.\n\n## Common Pitfalls\n\n| Level | Issue | Prevention |\n|-------|-------|------------|\n| CRITICAL | Generating legacy custom-flow code (`signIn.create` + `prepareFirstFactor` + `setActive`) | Use the current method-based API (Gate 4) |\n| CRITICAL | Using `useOAuth()` | Use `useSSO()` (Gate 5) |\n| CRITICAL | Implementing SMS\u002Fsocial auth without checking the factor is enabled | Check environment\u002Fdashboard first (Gate 3) |\n| CRITICAL | Native components targeted at Expo Go or web | Require a dev build; offer custom flows otherwise (Gate 8) |\n| CRITICAL | Sign-up screen missing `\u003CView nativeID=\"clerk-captcha\" \u002F>` | Always include it (Gate 10) |\n| HIGH | `NEXT_PUBLIC_` env prefix, or env var read inside `node_modules` | `EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY`, passed explicitly to `ClerkProvider` |\n| HIGH | Session lost on restart | `tokenCache` from `@clerk\u002Fexpo\u002Ftoken-cache` on the provider |\n| HIGH | Calling `setActive()` after `AuthView` \u002F `UserButton` auth | Native components sync sessions automatically |\n| HIGH | Pairing `AuthView` with `useSignInWithGoogle`\u002F`useSignInWithApple` | `AuthView` renders enabled social providers itself |\n| HIGH | Calling `WebBrowser.maybeCompleteAuthSession()` manually | `ClerkProvider` handles it |\n| HIGH | Splitting sign-in \u002F sign-up without being asked | Combined flow by default (Gate 9) |\n| MEDIUM | Missing `isLoaded` check before `isSignedIn` in guards | Always gate on `isLoaded` first |\n| MEDIUM | Using `yalc`\u002F`pnpm link` for local `@clerk\u002Fexpo` development | Use Verdaccio or pkg.pr.new |\n\n## See Also\n\n- `clerk` — top-level router\n- `clerk-swift` \u002F `clerk-android` — native mobile SDKs\n- `clerk-orgs`, `clerk-billing`, `clerk-webhooks` — feature skills (hooks work the same in Expo)\n- Installed package source: `node_modules\u002F@clerk\u002Fexpo\u002F`\n- https:\u002F\u002Fclerk.com\u002Fdocs\u002Fgetting-started\u002Fquickstart (Expo SDK tab)\n- https:\u002F\u002Fclerk.com\u002Fdocs\u002Freference\u002Fexpo\u002Foverview\n- https:\u002F\u002Fgithub.com\u002Fclerk\u002Fclerk-expo-quickstart — three official example apps: JS-only (Expo Go), JS + native sign-in buttons, native components\n",{"license":15,"metadata":24,"description":7},{"author":25,"version":26},"clerk","2.0.0","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fclerk-expo","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add NeelakshSaxena\u002FVayu --skill clerk-expo",{"tool":40,"command":41},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill clerk-expo",{"tool":43,"command":44},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill clerk-expo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002FSKILL.md",true,[48,54,58,62,66,70,74],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",6733,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcustom-flows.md",9526,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Freferences\u002Fcustom-flows.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fprebuilt-components.md",5033,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Freferences\u002Fprebuilt-components.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fprotected-routes.md",2550,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Freferences\u002Fprotected-routes.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Frecipes.md",5151,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Freferences\u002Frecipes.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fsetup.md",5177,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Freferences\u002Fsetup.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsso-and-native-auth.md",6171,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-expo\u002Freferences\u002Fsso-and-native-auth.md",[79,87,94,101,108,115],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]