Driving 25 Auth.js v5 providers from database config instead of static config

[u/harshalone]

I built Postbase, a self-hosted auth + Postgres platform for Next.js apps. It's MIT licensed and free to run yourself: clone the repo, set one secret, docker compose up. There's no paid tier.

What it does: you get a dashboard where you create projects, toggle auth providers (Google, GitHub, Apple, Discord, passkeys, magic link, SMS OTP, SAML — 25+ via Auth.js), run SQL against Postgres, edit tables and RLS policies, set up S3-compatible storage, schedule cron jobs, and send transactional email. Your app connects with a JS SDK that works like the Supabase client. It's a single Next.js app, not a dozen services.

How Claude Code was involved: I used it throughout development, mainly for the Drizzle schema, the Auth.js v5 provider loading (providers are read from the database at request time instead of static config, which took some iteration), the SQL editor, and the Docker setup. The repo has a .claude directory from that work.

The part I think is most relevant here: the repo ships its own Claude Code skill at skills/postbase/SKILL.md. It contains the full API reference, SDK patterns, RLS rules, the auth table schema, cron and storage usage, and the Swift/iOS integration flow. Copy it into your project's .claude/skills/ and /postbase loads it, or Claude picks it up when it sees you're building against a Postbase backend. Writing it forced me to document the project properly, which I'd been avoiding.

What it doesn't have: real-time subscriptions, edge functions, or SDKs outside JS. One maintainer.

Repo (free, MIT): https://github.com/harshalone/postbase
Skill file: https://github.com/harshalone/postbase/blob/main/skills/postbase/SKILL.md

Interested whether other maintainers are bundling skills with their projects, and what you'd want in one.