What problem does it solve? Adding authentication to a TypeScript or JavaScript app 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 a decision-tree implementation so the auth setup matches the project's actual stack. ## Core Features & Use Cases - Guided Planning Phase: Scans the project to auto-detect framework, database/ORM, existing auth libraries, and package manager, then asks structured questions about sign-in methods, providers, plugins, and UI style before writing code. - Framework-Specific Implementation: Provides route handler setup, client imports, and config patterns for Next.js, SvelteKit, Nuxt, Astro, Express, Hono, and SolidStart. - Database & Plugin Coverage: Includes adapter setup for Prisma, Drizzle, MongoDB, and raw drivers, plus plugin patterns for 2FA, organizations, admin, bearer tokens, passkeys, and SSO. - Use Case: A developer adding email/password plus Google and GitHub OAuth to an existing Next.js app with PostgreSQL and Prisma gets a confirmed plan, then step-by-step config files, migrations, and sign-in/sign-up pages. ## Quick Start Add authentication with email/password and Google OAuth to my Next.js app using Better Auth and Prisma.