← ClaudeAtlas

clerk-androidlisted

Implement Clerk authentication for native Android apps using Kotlin and Jetpack Compose with clerk-android source-guided patterns. Use for prebuilt AuthView/UserButton or custom API-driven auth flows. Do not use for Expo or React Native projects.
FJRG2007/enigma · ★ 2 · Web & Frontend · score 72
Install: claude install-skill FJRG2007/enigma
# Clerk Android (Native) This skill implements Clerk in native Android projects by following current `clerk-android` SDK and docs patterns. ## Activation Rules Activate this skill when either condition is true: - The user explicitly asks for Android, Kotlin, Jetpack Compose, or native mobile Clerk implementation on Android. - The project appears to be native Android (for example `build.gradle(.kts)` with Android plugins, `AndroidManifest.xml`, `app/src/main/java`, Compose UI files). Do not activate this skill when either condition is true: - The project is Expo. - The project is React Native. If Expo/React Native signals are present, route to the general setup skill instead. ## What Do You Need? | Task | Reference | |------|-----------| | Prebuilt AuthView / UserButton (fastest) | references/prebuilt.md | | Custom API-driven auth flows (full control) | references/custom.md | ## Quick Start | Step | Action | |------|--------| | 1 | Confirm project type is native Android and not Expo/React Native | | 2 | Determine flow type (`prebuilt` or `custom`) and load the matching reference file | | 3 | Ensure a real Clerk publishable key exists (or ask developer) | | 4 | Ensure correct Clerk artifacts are installed for the selected flow | | 5 | Read official Android quickstart and verify required setup (Native API, min SDK/Java, manifest, initialization) | | 6 | Inspect `clerk-android` source/sample patterns relevant to selected flow | | 7 | Implement flow by following only the