What problem does it solve? Adding authentication to a TypeScript or JavaScript project involves many decisions—framework integration, database adapters, OAuth providers, plugins, and UI pages—and mistakes in any of them cause broken sessions or security gaps. This Skill guides the full Better Auth setup from planning through implementation. ## Core Features & Use Cases - Project Detection & Planning: Scans the codebase to detect the framework (Next.js, SvelteKit, Nuxt, Astro, Express, Hono), database/ORM (Prisma, Drizzle, Mongoose), and package manager, then asks structured planning questions before writing code. - Full Implementation Guidance: Covers server config, client setup, route handlers, database migrations via the Better Auth CLI, OAuth providers, email verification, and plugins like 2FA, organizations, and admin. - Auth UI & Security: Walks through building sign-in/sign-up pages, session checks, protected routes, and a production security checklist. - Use Case: You have a SvelteKit app backed by Neon PostgreSQL and Drizzle. Use this Skill to detect the stack, configure the Drizzle adapter, set up the route handler, add Google and GitHub OAuth, and generate the auth schema migrations. ## Quick Start Add Better Auth authentication with email/password and Google OAuth to my existing Next.js project that uses Drizzle and PostgreSQL.
