neondatabase / neon-js

The three split cleanly by framework and scope. neon-auth-nextjs wires Neon Auth's API routes, middleware, server components, and UI into a Next.js App Router project. neon-auth-react does the same for a plain React app built with Vite or Create React App. neon-js-react is the superset of the React skill: the same setup plus a typed database client and generated database types, for a project that wants both auth and Neon's own data API. All three ship the same pre-built login forms and auth pages, so none of them requires designing an auth UI from scratch.

This is for a team that has already picked Neon as its Postgres provider and wants to use its own bundled @neondatabase/auth or @neondatabase/neon-js package instead of assembling NextAuth, Clerk, or a hand-rolled auth flow. Anyone on a different framework — SvelteKit, plain Express, a mobile client — has no skill here at all; the README only documents Next.js and React integration paths.

READ THE FULL ANALYSIS＋

What it costs to start. Our data labels the two auth-only skills, neon-auth-nextjs and neon-auth-react, as needing a Neon account and API key already in hand. neon-js-react is labeled as needing a local tool instead. In practice all three are setting up a connection to Neon's hosted service, so a Neon project is the real prerequisite either way.

The database-only path has no skill. The README's own decision tree names a third package, @neondatabase/postgrest-js, for database queries with no authentication attached — but none of the three live skills points at it. A reader who wants Neon's data API without Neon Auth has to read that package's own README directly rather than install a skill for it.