First-party. This plugin is built and maintained by ShipWithAI. Unlike the reviewed third-party tools in this toolkit, it is our own product — judge it accordingly.

Problem it solves

Auth is the part of a side project that eats a weekend. Not because any single step is hard, but because there are forty of them, they are spread across three consoles, and the failure modes are silent — a redirect URI that does not match, a session cookie that never sets on the production domain, a token refresh that works locally and not behind a proxy.

The plugin walks the whole path: choose a provider, wire OAuth, generate the UI pages and the database schema, and hand you a provider-specific README with the exact console steps and the pitfalls that apply to what you chose.

How to install

/plugin marketplace add ShipWithAI/shipwithai-plugins
/plugin install shipwithai-auth@shipwithai

How to use

/shipwithai-auth:setup # interactive wizard: provider, OAuth, ORM
/shipwithai-auth:doctor # diagnose an auth setup that is not working

Or skip the command and just describe what you want — the auth-setup skill activates on its own:

> Set up Firebase Auth with Google login for my Next.js app

Providers as of v1.7.1:

ProviderCostBest forStatus
Better AuthFree foreverSelf-hosted, full controlSupported
Firebase AuthFree under 50K MAUMobile / KMP, Google ecosystemSupported
ClerkFree under 10K MAUFastest setup, pre-built UIComing soon
Auth.jsFree foreverLightweight, educationalComing soon
Supabase AuthFree under 50K MAUPostgres-native, RLSComing soon

Pro tips

  • Answer the decision framework honestly rather than picking the provider you have heard of. Migrating auth later is the single most expensive refactor in a small product.
  • Read the generated README’s pitfall section before you deploy, not after the first bug report.
  • Run doctor before rerunning setup. Setup regenerates files; doctor tells you which one is actually wrong.

When NOT to use

Skip it if your framework already ships auth you are happy with, or if you need a provider that is still on the coming-soon list. And do not treat the output as audited — generated auth code is a starting point that still needs review.