New · free · runs in your browser

VibeBoot Doctor.
Paste what broke.

An error, a build log, a .env, middleware.ts or your package.json. You get the diagnosis, the fix and the Cursor rule that stops your AI agent from doing it again.

vibeboot doctor70 fixes
try:

› 70 fixes from the Next.js, Auth.js, Prisma and Stripe webhook fixers, plus .env, middleware.ts and package.json checks. You get the diagnosis, the fix and the rule that prevents it.

  • 70 verified fixes
  • 4 fixers + .env, middleware.ts, package.json
  • nothing leaves your browser
  • updated

01What it knows

One box, every fixer.

The Doctor scores your paste against every entry below and shows the best match first, with up to two runners-up. Each result links to the full entry, with causes, code and a prompt for Cursor or Claude Code.

The package.json check

  • next on a range or latest: an unpinned next lets every install build a different version (npm ci lockfile errors).
  • next and eslint-config-next drift: the two should move together.
  • Next.js 16: middleware.ts is now proxy.ts; older than 16 means some fixes need an upgrade first.
  • next-auth v4: v4 vs v5 API mix-ups (getServerSession vs auth()) and the old @next-auth/prisma-adapter.
  • Prisma: no prisma generate in build or postinstall (Vercel outdated client), prisma vs @prisma/client version mismatch.
  • stripe: points you at the raw-body webhook check, the most common App Router failure.

Every check maps to an entry the fixers already document. Prevention rules come from the free Cursor Rules Pack.

vibeboot saas starter

Starting your next project? The VibeBoot SaaS Starter ships auth, Stripe and a database already wired on Next.js 16.4.3, with AGENTS.md, CLAUDE.md and .cursor/rules for your AI agent. $49, one-time.

14-day money-back guarantee · lifetime updates

Get the SaaS StarterWhat's inside →

FAQ

Is my error or package.json sent anywhere?

No. The Doctor is plain JavaScript running in this page. It matches what you paste against the fixers' data in your browser. Nothing is sent, logged or stored.

Where do the fixes come from?

They're the same 70 entries as the Next.js, Auth.js, Prisma and Stripe webhook fixers on this site, each reproduced or checked against the versions listed on its page (for example Next.js 16.4.3, next-auth 5.0.0-beta.32, Prisma 6.19 and stripe-node 23.0.0). The Doctor routes your paste to the best entry and links to the full write-up.

What does the package.json check look at?

Only things the fixers already document: how next is pinned, next vs eslint-config-next, the Next.js 16 middleware rename, next-auth v4 vs v5, Prisma's generate step and prisma vs @prisma/client versions, and Stripe webhook verification. It doesn't guess about packages it has no data for.

What's the prevention rule?

Where a file in the free Cursor Rules Pack covers the problem, the Doctor links to it. Drop it in .cursor/rules and your agent stops writing that bug again. Where no rule covers it yet, the Doctor says so instead of inventing one.

It didn't match my error. What now?

Paste the first line of the error plus a few lines under it. If it still doesn't match, it isn't in the data yet; try the individual fixer pages or the Next.js docs.

$ fixed it? get the next one first

New fixes for what AI agents break, by email.

When we add a fix or a Cursor rule for a new Next.js, Auth.js, Prisma or Stripe break, it goes out in the VibeBoot newsletter. Free, occasional, unsubscribe in one click.

Subscribe free

> More free tools

All tools →