mcpbeat

Neon Auth

neondatabase/neon-auth

Sets up Neon Auth for your application. Configures authentication, creates auth routes, and generates UI components. Use when adding authentication to Next.js, React SPA, or Node.js projects.

8k tokens
context cost
the whole folder, loaded on every use
5
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
86
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/neondatabase/ai-rules --skill neon-auth

What comes with it

27 123 bytes besides the instruction
guides/nextjs-setup.md
guides/react-spa-setup.md
templates/auth-client.ts
templates/nextjs-api-route.ts

The instruction itself

9 sections, as written by the author

Neon Auth Integration

Add authentication to your application.

When to Use This Skill

  • Adding authentication to a new or existing project
  • Implementing sign-in, sign-up, and session management
  • Configuring social authentication (Google, GitHub)

Package: @neondatabase/auth (auth only, smaller bundle)

Need database queries too? Use the neon-js skill instead for @neondatabase/neon-js with unified auth + data API.

Code Generation Rules

When generating TypeScript/JavaScript code, follow these rules:

Complete reference: See Code Generation Rules for:

  • Import path handling (path aliases vs relative imports)
  • Neon package imports (subpath exports, adapter patterns)
  • CSS import strategy (Tailwind detection, single import method)
  • File structure patterns

Key points:

  • Check tsconfig.json for path aliases before generating imports
  • Use relative imports if unsure or no aliases exist
  • BetterAuthReactAdapter MUST be imported from auth/react/adapters subpath
  • Adapters are factory functions - call them with ()
  • Choose ONE CSS import method (Tailwind or CSS, not both)

Available Guides

Each guide is a complete, self-contained walkthrough with numbered phases:

  • guides/nextjs-setup.md - Complete Next.js App Router setup guide
  • guides/react-spa-setup.md - Detailed React SPA guide with react-router-dom integration

I'll automatically detect your context (package manager, framework, existing setup) and select the appropriate guide based on your request.

For troubleshooting, see the Troubleshooting Guide in references.

Quick Examples

Tell me what you're building - I'll handle the rest:

  • "Add authentication to my Next.js app" -> Loads setup guide, sets up auth routes
  • "Set up sign-in with Google" -> Configures social auth provider
  • "Debug my auth session not persisting" -> Loads troubleshooting guide

Reference Documentation

Primary Resource: See neon-auth.mdc for comprehensive guidelines including:

  • All authentication methods (email/password, social, magic link)
  • Session data structure
  • UI components reference
  • Error handling

Framework-Specific Setup (choose your framework):

Framework-Specific UI (choose your framework):

Shared References:

Templates

  • templates/nextjs-api-route.ts - API route handler for Next.js
  • templates/auth-client.ts - Client-side auth configuration
  • neon-js - Full SDK with auth + database queries (use if you need PostgREST-style data access)
  • neon-drizzle - Drizzle ORM setup (for database queries)
  • neon-serverless - Direct database connections
  • add-neon-docs - Add Neon best practices to your project (run after setup)

Workflow

I will:

  • Detect your project context automatically (Next.js, React SPA, Node.js)
  • Select and load the appropriate guide
  • Follow the guide's phases sequentially
  • Track progress using the guide's workflow checklist
  • Load reference files only when needed
  • Offer to add Neon best practices to your project docs

Ready to get started? Just describe what you're building!

How to use it

Copy the folder

Take neondatabase/neon-auth from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.