auth-provider
Installation
SKILL.md
Auth Provider Integration
Purpose
Building auth from scratch is months of work: password reset flows, email verification, brute-force protection, MFA, session management, token rotation. Managed auth providers handle all of this. This skill's job is to integrate them correctly so the rest of the application gets a trusted user object without knowing or caring how the session was established.
Step 1 - Choose the Right Path
| Scenario | Best Choice |
|---|---|
| Users want "Sign in with Google/GitHub" on top of your own auth | OAuth via FastAPI + next-auth |
| You want fully managed auth (email, social, MFA, user dashboard) | Clerk (best DX for vibe-coders) |
| You're already using Supabase for DB | Supabase Auth |
| Enterprise SSO (SAML, OIDC) or highly customizable | Auth0 |
| Want control but not from scratch | FastAPI custom JWT (see security skill) |
SOP: Clerk (Recommended for New Projects)
Clerk handles the entire auth layer: sign-up/in UI, email magic links, Google/GitHub OAuth, MFA, and a user management dashboard. You own none of the auth complexity.