better-auth-best-practices
better-auth/skills
Configure Better Auth server and client with database adapters, sessions, plugins, and OAuth.
What is better-auth-best-practices?
Better Auth is a TypeScript authentication framework for setting up email/password, OAuth, and plugin-based auth flows. Use this skill when implementing Better Auth in a project, configuring database adapters (Prisma, Drizzle, MongoDB), managing sessions, or adding authentication plugins.
- Install and configure Better Auth server with database adapters (Drizzle, Prisma, MongoDB, built-in)
- Set up email/password authentication, OAuth providers, and social login
- Manage sessions with cookie caching strategies (compact, JWT, JWE) and optional secondary storage (Redis/KV)
- Configure plugins (two-factor, passkeys, magic links, organizations, API keys, SSO)
- Handle environment variables (BETTER_AUTH_SECRET, BETTER_AUTH_URL) and security settings
- Create client integrations for vanilla JS, React, Vue, Svelte, and Solid
How to install better-auth-best-practices
npx skills add https://github.com/better-auth/skills --skill better-auth-best-practices- Node.js project with npm or compatible package manager
- Database (PostgreSQL, MySQL, SQLite, MongoDB) or serverless alternative (Neon, PlanetScale)
- Optional: Drizzle, Prisma, or MongoDB driver already installed
How to use better-auth-best-practices
- 1.Run `npm install better-auth` to add the package
- 2.Set environment variables: `BETTER_AUTH_SECRET` (min 32 chars, generate with `openssl rand -base64 32`) and `BETTER_AUTH_URL`
- 3.Create `auth.ts` in project root, `./lib`, `./utils`, or `./src` with database config and auth options
- 4.Create a route handler for your framework (e.g., `/api/auth/[...auth].ts` for Next.js)
- 5.Run migrations: `npx auth@latest migrate` (built-in), `npx drizzle-kit push` (Drizzle), or `npx prisma migrate dev` (Prisma)
- 6.Verify setup by calling `GET /api/auth/ok` — should return `{ status: "ok" }`
- 7.Add plugins by importing from dedicated paths (e.g., `from "better-auth/plugins/two-factor"`) and re-run migrations
Use cases
- Setting up a new TypeScript app with email/password and Google OAuth authentication
- Migrating an existing auth system to Better Auth with Drizzle or Prisma ORM
- Adding two-factor authentication or passkey support via plugins
- Configuring session storage in Redis for distributed applications
- Implementing role-based access control and organization management with plugins
- Full-stack TypeScript developers
- Backend engineers building authentication systems
- Teams using Drizzle, Prisma, or MongoDB for data persistence
- Developers needing OAuth and multi-provider authentication
- Projects requiring plugin-based auth extensibility
better-auth-best-practices FAQ
Prefer env vars for production. Only define `baseURL` and `secret` in the config if the corresponding env vars are NOT set.
The CLI looks for `auth.ts` in `./`, `./lib`, `./utils`, or under `./src`. Use `--config` flag to specify a custom path.
If `secondaryStorage` (Redis/KV) is defined, sessions go there by default. Set `session.storeSessionInDatabase: true` to also persist to the database. Without secondary storage, sessions use the database or cookie cache.
The `drizzleAdapter(db, ...)` requires a `db` instance from `drizzle()`. Ensure you've created the Drizzle client with your database driver (node-postgres, postgres.js, Neon, etc.) before passing it to the adapter.
Re-run the CLI migration command (`npx auth@latest migrate` or `npx auth@latest generate`) to update the database schema with the plugin's tables and fields.
Full instructions (SKILL.md)
Source of truth, from better-auth/skills.
name: better-auth-best-practices description: Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables. Use when users mention Better Auth, betterauth, auth.ts, or need to set up TypeScript authentication with email/password, OAuth, or plugin configuration.
Better Auth Integration Guide
Documentation Version
Use documentation that matches the Better Auth version installed in the project. APIs and plugin names can differ across maintained release lines.
- Prefer a version explicitly named by the user.
- Otherwise, inspect the resolved
better-authversion in the lockfile, falling back to the package manifest when no lockfile is available. - When the Better Auth MCP is available, call
get_docwith/llms.txtto resolve that package version to a documentation identifier. Pass the identifier to everysearch_docscall and pass result paths toget_docunchanged. - Without MCP, start at better-auth.com/llms.txt and follow the matching version index.
- Use the latest documentation only when the project version cannot be determined or the user explicitly asks about the latest release or an upgrade.
When planning an upgrade, separate guidance for the currently installed version from guidance for the target version.
Setup Workflow
- Install:
npm install better-auth - Set env vars:
BETTER_AUTH_SECRETandBETTER_AUTH_URL - Create
auth.tswith database + config - Create route handler for your framework
- Run migrations:
- Built-in adapter:
npx auth@latest migrate - Drizzle:
npx auth@latest generate --output src/db/auth-schema.tsthennpx drizzle-kit push(dev) ornpx drizzle-kit generate && npx drizzle-kit migrate(prod) - Prisma:
npx auth@latest generate --output prisma/schema.prismathennpx prisma migrate dev
- Built-in adapter:
- Verify: call
GET /api/auth/ok— should return{ status: "ok" }
Quick Reference
Environment Variables
BETTER_AUTH_SECRET- Encryption secret (min 32 chars). Generate:openssl rand -base64 32BETTER_AUTH_URL- Base URL (e.g.,https://example.com)
Only define baseURL/secret in config if env vars are NOT set.
File Location
CLI looks for auth.ts in: ./, ./lib, ./utils, or under ./src. Use --config for custom path.
CLI Commands
npx auth@latest migrate- Apply schema (built-in adapter)npx auth@latest generate- Generate schema for Prisma/Drizzlenpx auth@latest mcp --cursor- Add MCP to AI tools
Re-run after adding/changing plugins.
Core Config Options
| Option | Notes |
|---|---|
appName | Optional display name |
baseURL | Only if BETTER_AUTH_URL not set |
basePath | Default /api/auth. Set / for root. |
secret | Only if BETTER_AUTH_SECRET not set |
database | Required for most features. See adapters docs. |
secondaryStorage | Redis/KV for sessions & rate limits |
emailAndPassword | { enabled: true } to activate |
socialProviders | { google: { clientId, clientSecret }, ... } |
plugins | Array of plugins |
trustedOrigins | CSRF whitelist |
Database
Direct connections: Pass pg.Pool, mysql2 pool, better-sqlite3, or bun:sqlite instance. For Postgres, also supports postgres (postgres.js) and @neondatabase/serverless.
ORM adapters: Import from better-auth/adapters/drizzle, better-auth/adapters/prisma, better-auth/adapters/mongodb.
Drizzle provider values: "pg" (PostgreSQL), "mysql" (MySQL), "sqlite" (SQLite). Must match the driver used.
Critical: Better Auth uses adapter model names, NOT underlying table names. If Prisma model is User mapping to table users, use modelName: "user" (Prisma reference), not "users".
Session Management
Storage priority:
- If
secondaryStoragedefined → sessions go there (not DB) - Set
session.storeSessionInDatabase: trueto also persist to DB - No database +
cookieCache→ fully stateless mode
Cookie cache strategies:
compact(default) - Base64url + HMAC. Smallest.jwt- Standard JWT. Readable but signed.jwe- Encrypted. Maximum security.
Key options: session.expiresIn (default 7 days), session.updateAge (refresh interval), session.cookieCache.maxAge, session.cookieCache.version (change to invalidate all sessions).
User & Account Config
User: user.modelName, user.fields (column mapping), user.additionalFields, user.changeEmail.enabled (disabled by default), user.deleteUser.enabled (disabled by default).
Account: account.modelName, account.accountLinking.enabled, account.storeAccountCookie (for stateless OAuth).
Required for registration: email and name fields.
Email Flows
emailVerification.sendVerificationEmail- Must be defined for verification to workemailVerification.sendOnSignUp/sendOnSignIn- Auto-send triggersemailAndPassword.sendResetPassword- Password reset email handler
Security
In advanced:
useSecureCookies- Force HTTPS cookiesdisableCSRFCheck- ⚠️ Security riskdisableOriginCheck- ⚠️ Security riskcrossSubDomainCookies.enabled- Share cookies across subdomainsipAddress.ipAddressHeaders- Custom IP headers for proxiesdatabase.generateId- Custom ID generation or"serial"/"uuid"/false
Rate limiting: rateLimit.enabled, rateLimit.window, rateLimit.max, rateLimit.storage ("memory" | "database" | "secondary-storage").
Hooks
Endpoint hooks: hooks.before / hooks.after - Array of { matcher, handler }. Use createAuthMiddleware. Access ctx.path, ctx.context.returned (after), ctx.context.session.
Database hooks: databaseHooks.user.create.before/after, same for session, account. Useful for adding default values or post-creation actions.
Hook context (ctx.context): session, secret, authCookies, password.hash()/verify(), adapter, internalAdapter, generateId(), tables, baseURL.
Plugins
Import from dedicated paths for tree-shaking:
import { twoFactor } from "better-auth/plugins/two-factor"
NOT from "better-auth/plugins".
Popular plugins: twoFactor, organization, passkey, magicLink, emailOtp, username, phoneNumber, admin, apiKey, bearer, jwt, multiSession, sso, oauthProvider, oidcProvider, openAPI, genericOAuth.
Client plugins go in createAuthClient({ plugins: [...] }).
Client
Import from: better-auth/client (vanilla), better-auth/react, better-auth/vue, better-auth/svelte, better-auth/solid.
Key methods: signUp.email(), signIn.email(), signIn.social(), signOut(), useSession(), getSession(), revokeSession(), revokeSessions().
Type Safety
Infer types: typeof auth.$Infer.Session, typeof auth.$Infer.Session.user.
For separate client/server projects: createAuthClient<typeof auth>().
Common Gotchas
- Model vs table name - Config uses ORM model name, not DB table name
- Plugin schema - Re-run CLI after adding plugins
- Secondary storage - Sessions go there by default, not DB
- Cookie cache - Custom session fields NOT cached, always re-fetched
- Stateless mode - No DB = session in cookie only, logout on cache expiry
- Change email flow - Sends to current email first, then new email
- Drizzle: db not initialized -
drizzleAdapter(db, ...)requires adbinstance fromdrizzle(). Seecreate-authskill for setup examples (node-postgres, postgres.js, Neon). - Drizzle: missing drizzle.config.ts -
drizzle-kitcommands require adrizzle.config.tspointing to the generated schema file and DB credentials.
Resources
Related skills
More from better-auth/skills and the wider catalog.

better-auth-security-best-practices
Secure Better Auth deployments with rate limiting, CSRF protection, session hardening, and audit logging.

create-auth
Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth with framework detection and OAuth setup.

create-auth
Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth

email-and-password-best-practices
Configure email verification, password reset flows, and security policies for Better Auth email/password authentication.

organization-best-practices
Configure multi-tenant organizations, roles, permissions, and teams with Better Auth's organization plugin.

two-factor-authentication-best-practices
Configure TOTP, OTP, backup codes, and trusted devices for 2FA with Better Auth.