mcpField
N
neon-js

neon-js

github.com/neondatabaseDevelopment86143 installsUpdated 39w ago
Repository

About neon-js

neon-js is a skill for integrating Neon’s unified JavaScript SDK in applications that need authentication and database queries. It provides setup guidance, PostgREST-style data access references, and help with type generation and migration.

Key features

  1. 01Configure authentication and data API clients
  2. 02Query databases with PostgREST-style syntax
  3. 03Use type-generation query workflows
  4. 04Reference BetterAuth and Supabase adapters
  5. 05Follow setup guides and code templates

Use cases

  1. 01Set up auth and data access in a Next.js app
  2. 02Add database queries to an existing auth setup
  3. 03Migrate an application from Supabase to Neon
  4. 04Configure generated types for database queries

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/neondatabase/ai-rules --skill neon-js

After installing, type/neon-jsin Claude Code to confirm it loaded.

Bundled filesguides/setup.mdtemplates/full-client.ts

Details

From the project README

Neon JS SDK Integration

Set up the unified Neon JS SDK for authentication and database queries in one package.

When to Use This Skill

  • Building apps that need both auth and database queries
  • Migrating from Supabase to Neon
  • Using PostgREST-style API for database access
  • Need type-safe database queries with generated types

Package: @neondatabase/neon-js (full SDK with auth + data API)

Need auth only? Use the neon-auth skill instead for @neondatabase/auth with a smaller bundle.

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/setup.md - Complete setup guide for Next.js with auth + data API

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:

  • "Set up Neon JS for my Next.js app" -> Loads full stack guide, configures auth + data
  • "Add database queries to my auth setup" -> Configures data API client
  • "Migrate from Supabase" -> Uses SupabaseAuthAdapter for compatibility

Reference Documentation

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

  • Client setup for all frameworks
  • Database query patterns (PostgREST syntax)
  • Auth adapter options (BetterAuth, Supabase)
  • Type generation
  • Error handling

Auth Details: See neon-auth.mdc for:

  • All authentication methods
  • UI components
  • Session management

Framework-Specific Setup (choose your framework):

Framework-Specific UI (choose your framework):

Data API & Shared References:

Templates

  • templates/full-client.ts - Unified auth + data client configuration

Related Skills

  • neon-auth - Auth only (smaller bundle, no data queries)
  • neon-drizzle - Drizzle ORM setup (alternative to PostgREST)
  • neon-serverless - Direct database connections
  • add-neon-docs - Add Neon best practices to your project (run after setup)

Workflow

I will:

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

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

Comments

Markdown supported