What problem does it solve?
This Skill removes uncertainty and manual work when adding Clerk authentication to native Android projects by providing clear, source-driven patterns, flow choices (prebuilt vs custom), and mandatory verification checks so developers can integrate auth correctly and safely.
Core Features & Use Cases
- Prebuilt and Custom Flows: Guides integration using prebuilt Compose views (AuthView/UserButton) or a custom API-driven implementation with clerk-android-api.
- Safety and Verification Gates: Enforces asking for flow choice and a real publishable key, SDK initialization checks, correct artifact selection, and runtime capability gating to avoid misconfiguration.
- Use Case: Add sign-in and profile UIs to a Kotlin + Jetpack Compose app using AuthView for fastest path or implement a multi-step custom flow that respects dashboard-driven factors and MFA.
Quick Start
Set up Clerk on my native Android Kotlin app by confirming it's a native project, choosing prebuilt or custom flow, providing the publishable key, and following the matching reference file (references/prebuilt.md or references/custom.md).