What problem does it solve? Adding authentication to a web application involves many decisions—framework integration, database adapters, OAuth providers, plugins, and UI pages—and mistakes in any of them create security risks. This Skill guides the process with a structured planning phase and framework-specific implementation steps for Better Auth. ## Core Features & Use Cases - Guided Planning Phase: Scans the project to detect the framework, ORM, existing auth libraries, and package manager, then asks structured questions about auth methods, providers, and features before writing code. - Framework-Specific Implementation: Provides route handler setups for Next.js, SvelteKit, Nuxt, Astro, Express, Hono, and SolidStart, plus database adapter configuration for Prisma, Drizzle, Kysely, and MongoDB. - Plugin and UI Support: Covers plugins like two-factor authentication, organizations, admin, bearer tokens, and passkeys, along with sign-in/sign-up page implementation and a security checklist. - Use Case: A developer adding login to an existing Next.js app with PostgreSQL and Prisma can follow the plan to configure email/password plus Google OAuth, run schema migrations, and build the auth pages. ## Quick Start Add authentication with Better Auth to my Next.js project using email/password and GitHub OAuth with a Prisma PostgreSQL database.
