What problem does it solve? Adding login and signup to a Convex app involves choosing an auth provider, wiring auth.config.ts, protecting backend functions, and mapping user identities, and getting any step wrong leaves the app unauthenticated or insecure. ## Core Features & Use Cases - Provider Selection Guidance: Detects or asks which provider to use among Convex Auth, Clerk, WorkOS AuthKit, Auth0, or a custom JWT provider before writing setup code. - Provider-Specific References: Ships detailed reference files for each provider covering env vars, auth.config.ts, client provider wiring, gotchas, and validation steps. - Backend Protection Patterns: Shows how to protect queries and mutations with ctx.auth.getUserIdentity() instead of trusting client-provided user IDs, plus role-based access control where needed. - Use Case: A developer says "add auth to my Convex app" and the skill walks through picking Clerk, configuring the issuer domain, wrapping the app in ClerkProvider and ConvexProviderWithClerk, and verifying authenticated queries work. ## Quick Start Set up authentication for this Convex app, figure out the right provider first, then wire up login, protected queries, and user identity mapping.