better-auth-knowledge-patch

Provide versioned knowledge patches for Better Auth v1.2–1.5 APIs and configurations.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill better-auth-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: better-auth-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/better-auth-knowledge-patch/skills/better-auth-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill better-auth-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This knowledge patch closes gaps left by model training cutoffs for Better Auth by providing verified, versioned guidance so developers avoid outdated APIs, insecure defaults, and migration errors when upgrading or integrating authentication systems.

Core Features & Use Cases

  • Versioned Knowledge Patches: Summarizes changes from v1.2 through v1.5 including OAuth 2.1 provider, Agent Auth protocol, cookie cache strategies, API key relocation, Stripe billing, i18n, and SSO/SAML SLO.
  • Migration & Upgrade Guidance: Includes CLI usage, import path and adapter migrations, breaking-change mappings, and dual-module hazard fixes to support safe upgrades.
  • Framework & Integration Patterns: Concrete integration notes and handlers for Next.js, SvelteKit, Expo, Electron, Convex, server adapters, and plugin creation patterns to simplify real-world adoption.

Quick Start

Use this patch before making or reviewing any Better Auth changes to align your code and configuration with v1.2–1.5 behavior and breaking changes.

Frequently Asked Questions about better-auth-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Better Auth imports and adapters when upgrading to v1.2 or later?

Better Auth integration patterns for Next.js, SvelteKit, Expo, Electron, and Convex are provided through concrete handler notes and server adapter configurations. These patches simplify real-world framework adoption by detailing specific integration behaviors and plugin creation patterns.

Does Better Auth support OAuth 2.1 provider and Agent Auth protocol configurations?

Better Auth handles API key relocation, Stripe billing schema changes, and SSO/SAML SLO by providing verified, versioned guidance that closes training cutoff gaps. This ensures developers apply the correct schema updates and avoid insecure defaults during configuration.

What is the best way to keep Better Auth configurations secure and aligned with v1.5?

You need this Better Auth knowledge patch if your model training cutoff predates v1.2, causing you to risk outdated APIs, insecure defaults, or migration errors. It provides verified guidance for upgrading and integrating authentication systems safely across web and native frameworks.

Why does my Better Auth upgrade fail with dual-module hazards or breaking changes?

Your Better Auth upgrade fails with dual-module hazards because v1.2 through v1.5 introduced breaking changes to import paths and adapters. Applying versioned knowledge patches maps these breaking changes and provides the necessary fixes to resolve dual-module conflicts during migration.