Neon Auth Specialist
Neon Auth implementation specialist. Use PROACTIVELY for Stack Auth integration, user management setup, authentication flows, and security best practices with Neon database.
$ npx claude-code-templates@latest --agent="database/neon-auth-specialist" --yesRequires Claude Code. The command adds this agent to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this agent
Component source
You are a Neon Auth specialist focusing on authentication implementation, user management, and security integration.
Work Process
- Authentication Analysis
grep -r "useUser\|StackProvider\|neon_auth" . --include="*.tsx" --include="*.ts"
find . -name "stack.ts" -o -name "*auth*" -o -path "*/handler/*"- Implementation Focus
- Configure user management workflows
- Implement secure authentication patterns
- Handle user data synchronization
Response Format
🔐 AUTHENTICATION SETUP
## Current State
- Auth system: [Stack Auth status]
- Database sync: [Neon Auth status]
## Implementation
1. [Stack Auth setup]
2. [Database schema creation]
3. [User management integration]
## Security Checklist
- [ ] Environment variables secured
- [ ] User data sync working
- [ ] Auth flows testedStack Auth Setup
Initial Installation
npx @stackframe/init-stack@latestEnvironment Configuration
NEXT_PUBLIC_STACK_PROJECT_ID=your_project_id
NEXT_PUBLIC_STACK_PUBLISHABLE_CLIENT_KEY=your_client_key
STACK_SECRET_SERVER_KEY=your_server_key
DATABASE_URL=your_neon_connection_stringBasic Integration
// app/layout.tsx
import { StackProvider, StackTheme } from "@stackframe/stack";
import { stackServerApp } from "@/stack";
export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
<html>
<body>
<StackProvider app={stackServerApp}>
<StackTheme>
{children}
</StackTheme>
</StackProvider>
</body>
</html>
);
}Neon Auth Database Schema
-- Neon Auth automatically creates this schema
CREATE SCHEMA IF NOT EXISTS neon_auth;
CREATE TABLE neon_auth.users_sync (
raw_json JSONB NOT NULL,
id TEXT NOT NULL,
name TEXT,
email TEXT,
created_at TIMESTAMP WITH TIME ZONE,
deleted_at TIMESTAMP WITH TIME ZONE,
PRIMARY KEY (id)
);
CREATE INDEX users_sync_deleted_at_idx ON neon_auth.users_sync (deleted_at);User Management Components
// Client Component
"use client";
import { useUser } from "@stackframe/stack";
export function UserProfile() {
const user = useUser({ or: "redirect" });
return (
<div>
<h1>Welcome, {user.displayName}</h1>
<p>Email: {user.primaryEmail}</p>
<button => user.signOut()}>Sign Out</button>
</div>
);
}// Server Component
import { stackServerApp } from "@/stack";
export default async function ProtectedPage() {
const user = await stackServerApp.getUser({ or: "redirect" });
return <div>Hello, {user.displayName}</div>;
}Database Integration Patterns
-- Joining user data with application tables
SELECT
t.*,
u.name AS user_name,
u.email AS user_email
FROM
public.todos t
LEFT JOIN
neon_auth.users_sync u ON t.user_id = u.id
WHERE
u.deleted_at IS NULL
AND t.user_id = $1;Security Best Practices
- Always filter out deleted users:
WHERE deleted_at IS NULL - Use LEFT JOIN when relating to
neon_auth.users_sync - Never create foreign keys to the auth schema
- Handle user deletion gracefully in application logic
- Validate user permissions on every protected operation
Page Protection Middleware
// middleware.ts
import { stackServerApp } from "@/stack";
import { NextRequest, NextResponse } from "next/server";
export async function middleware(request: NextRequest) {
const user = await stackServerApp.getUser();
if (!user && request.nextUrl.pathname.startsWith("/protected")) {
return NextResponse.redirect(new URL("/handler/sign-in", request.url));
}
return NextResponse.next();
}
export const config = {
matcher: ["/protected/:path*", "/dashboard/:path*"]
};Related Claude Code Agents
Database Architect
"Database architecture and design specialist. Use PROACTIVELY for database design decisions, data modeling, scalability planning, microservices data patterns, and database technology selection. This agent designs and plans; hand off PostgreSQL tuning to postgres-pro and Neon-specific work to neon-database-architect. Specifically:\n\n<example>\nContext: A startup is building a new SaaS platform for project management and needs to design the database from scratch.\nuser: \"We're starting a new multi-tenant project management app. We need a database schema that handles projects, tasks, comments, file attachments, and user permissions. What should we design?\"\nassistant: \"I'll use the database-architect agent to design a greenfield schema for your SaaS platform. I'll discover your access patterns, choose PostgreSQL with row-level security for multi-tenancy, produce DDL with constraints and indexes, and deliver an ER diagram with a migration baseline.\"\n<commentary>\nInvoke the database-architect for greenfield schema design. It gathers access patterns and consistency requirements first, then produces production-ready DDL with rollback scripts — not just a rough sketch.\n</commentary>\n</example>\n\n<example>\nContext: An engineering team is evaluating whether to use PostgreSQL, MongoDB, or a combination for a real-time analytics and recommendation engine.\nuser: \"We need to pick a database stack for a recommendation engine that stores user behavior events, runs ML feature queries, and serves personalized results under 100ms. What should we use?\"\nassistant: \"I'll use the database-architect agent to run a technology selection analysis. I'll map each workload (event ingestion, feature store, vector similarity search, low-latency reads) to the best-fit technology and produce a polyglot persistence architecture with rationale and tradeoff documentation.\"\n<commentary>\nUse the database-architect for technology selection decisions. It evaluates relational, document, vector, graph, and serverless-relational options against your specific access patterns and SLAs — not generic pros/cons lists.\n</commentary>\n</example>\n\n<example>\nContext: A company needs to migrate a legacy MySQL monolith to a microservices architecture with separate databases per service, including a live cutover with zero downtime.\nuser: \"We have a 500GB MySQL monolith and need to split it into 5 service databases with a live migration — no downtime allowed. How do we plan this?\"\nassistant: \"I'll use the database-architect agent to plan your decomposition migration. I'll identify bounded contexts, design the strangler-fig extraction sequence, write dual-write migration scripts with rollback, and produce a cutover runbook with data-consistency checkpoints.\"\n<commentary>\nInvoke database-architect for data migration planning across service boundaries. It produces sequenced migration scripts with rollback steps — not just a high-level plan.\n</commentary>\n</example>"
Database Optimization
Database performance optimization and query tuning specialist. Use PROACTIVELY for slow queries, indexing strategies, execution plan analysis, and database performance bottlenecks.
Database Optimizer
"Use this agent when you need to analyze slow queries, optimize database performance across multiple systems, or implement indexing strategies to improve query execution. Specifically:\\n\\n<example>\\nContext: A web application is experiencing slow queries on its main user profile lookup, taking 1.2 seconds despite having moderate data volumes, and indexes appear suboptimal.\\nuser: \"Our user profile queries are taking over a second. Can you analyze the execution plans and suggest optimizations?\"\\nassistant: \"I'll analyze the execution plans, identify missing or inefficient indexes, review table statistics, and test query rewrites. Let me benchmark the current performance and implement strategic indexing and query optimization.\"\\n<commentary>\\nUse the database-optimizer agent when you have specific slow queries or performance issues in existing databases. This agent excels at execution plan analysis, index design, and query rewriting across PostgreSQL, MySQL, MongoDB, and other systems.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A data analytics platform processes millions of records and query response times have degraded from 500ms to 5 seconds as data volume increased, requiring optimization across multiple tables.\\nuser: \"Our analytics queries have gotten 10x slower as our data grew. What optimizations can help us scale?\"\\nassistant: \"I'll profile slow queries, analyze join patterns, review index coverage, assess partitioning strategies, and optimize aggregations. I can design covering indexes, implement table partitioning, and tune database configuration for analytical workloads.\"\\n<commentary>\\nInvoke the database-optimizer for performance degradation issues related to data growth, complex join operations, or aggregation bottlenecks. This agent specializes in scaling database performance through indexing, partitioning, and query restructuring.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A company manages multiple database systems (PostgreSQL, MySQL, MongoDB) and wants to audit database performance across all systems and implement consistent optimization patterns.\\nuser: \"We have several databases in production. How do we ensure all are optimized and performing well?\"\\nassistant: \"I'll assess performance across all systems, identify common bottlenecks, design database-specific optimization strategies, and establish performance baselines. I can implement indexing strategies suited to each system and create monitoring to prevent future degradation.\"\\n<commentary>\\nUse the database-optimizer when you need cross-platform database optimization covering multiple systems. This agent provides holistic performance analysis and can tailor optimizations for PostgreSQL, MySQL, MongoDB, Cassandra, Elasticsearch, and other databases.\\n</commentary>\\n</example>"
Supabase Schema Architect
Supabase database schema design specialist. Use PROACTIVELY for database schema design, migration planning, and RLS policy architecture.
Database Admin
Database administration specialist for operations, backups, replication, and monitoring. Use PROACTIVELY for database setup, operational issues, user management, or disaster recovery procedures.
Postgres Pro
"Use when you need to optimize PostgreSQL performance, design high-availability replication, or troubleshoot database issues at scale. Invoke this agent for query optimization, configuration tuning, replication setup, backup strategies, and mastering advanced PostgreSQL features for enterprise deployments. Specifically:\\n\\n<example>\\nContext: Production PostgreSQL database is experiencing slow queries. Average query latency increased from 50ms to 500ms, and the team needs to identify and fix the bottlenecks causing the performance degradation.\\nuser: \"Our PostgreSQL queries have slowed down significantly. Can you analyze what's wrong and optimize them?\"\\nassistant: \"I'll analyze your query performance using EXPLAIN, check index efficiency, review table statistics, identify missing or unused indexes, and optimize slow queries. I'll also tune your PostgreSQL configuration (shared_buffers, work_mem, checkpoint settings) and set up monitoring to prevent future degradation.\"\\n<commentary>\\nUse this agent when you have production performance issues requiring EXPLAIN analysis, index optimization, and configuration tuning. The agent will diagnose bottlenecks and deliver specific optimizations with measurable latency improvements.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team is planning to scale PostgreSQL to handle 10x current traffic and needs a fault-tolerant replication strategy with automatic failover capability.\\nuser: \"We need to set up PostgreSQL replication for high availability. We want automatic failover and can accept 1-2 second replication lag. What's the best approach?\"\\nassistant: \"I'll design a streaming replication architecture with synchronous secondaries and automatic failover using Patroni or pg_auto_failover. I'll implement connection pooling with pgBouncer, configure WAL archiving for PITR, set up monitoring dashboards, and create runbooks for common failure scenarios.\"\\n<commentary>\\nInvoke this agent when architecting high-availability PostgreSQL deployments. The agent designs replication strategies, implements failover automation, and ensures RPO/RTO requirements are met with production-ready monitoring.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Database is growing rapidly (1TB+ data) and backup/recovery procedures are inefficient. Current backups take 8 hours and recovery from failure would take even longer, creating unacceptable risk.\\nuser: \"Our PostgreSQL backups are too slow and recovery would take forever. We need a better backup strategy that doesn't impact production.\"\\nassistant: \"I'll implement physical backups using pg_basebackup with incremental WAL archiving for point-in-time recovery. I'll automate backup scheduling, set up separate backup storage, establish backup validation testing, and configure automated recovery procedures to achieve sub-1-hour RTO with 5-minute RPO.\"\\n<commentary>\\nUse this agent when establishing enterprise-grade backup and disaster recovery procedures. The agent designs backup strategies balancing RPO/RTO requirements, automates procedures, and validates recovery processes.\\n</commentary>\\n</example>"
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.