auth-schema

Regenerate the Better Auth Convex schema from the auth config using the Better Auth CLI.

20|5|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/tale-project/tale --skill auth-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-schema
Source: https://github.com/tale-project/tale/tree/main/.claude/skills/auth-schema
Command: npx skills add https://github.com/tale-project/tale --skill auth-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate the Better Auth Convex schema to reflect the current authentication config and prevent drift between config and the generated schema.

Core Features & Use Cases

  • Regenerate the generated_schema.ts from the auth config using the Better Auth CLI when auth models change.
  • Validate that config changes and schema updates stay in sync, then commit the updated generated_schema.ts with the change.
  • Use cases include updating user roles, plugins like twoFactor or passkeys, and re-aligning schema after deployment changes.

Quick Start

Run the Better Auth CLI regeneration from the services/platform directory and commit the updated generated_schema.ts alongside the config changes.

Frequently Asked Questions about auth-schema

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

FAQPage Schema
How do I regenerate the Better Auth schema after updating my authentication config?

To regenerate the Better Auth schema, run the Better Auth CLI from the services/platform directory. This updates the generated_schema.ts to reflect auth config changes and prevents drift between the config and the generated schema.

Why does my Convex schema drift after changing Better Auth plugins like twoFactor or passkeys?

Convex schema drift occurs when authentication models change but the generated schema is not updated. Regenerating the generated_schema.ts via the Better Auth CLI realigns the schema with current auth config and plugin definitions.

When do I need to regenerate the generated_schema.ts in my Convex project?

You need to regenerate the generated_schema.ts when you update user roles, add Better Auth plugins, or detect schema drift after running a Convex push or tsc type check against your authentication model.

What is the correct workflow to commit regenerated Better Auth schema updates?

The correct workflow is to run the Better Auth CLI regeneration from the services/platform directory, validate that the config and schema are in sync, and commit the updated generated_schema.ts alongside your original config changes.

Can I update my auth models in auth.ts without regenerating the Convex schema?

Updating auth models in auth.ts without regenerating the Convex schema leaves the generated_schema.ts out of sync. You must run the Better Auth CLI to regenerate the schema and prevent deployment drift.

Does Better Auth work with Convex to automatically sync schema after a push?

Better Auth does not automatically sync the schema after a Convex push. You must manually run the Better Auth CLI from the services/platform directory to regenerate the generated_schema.ts and resolve any detected drift.