davila7
Instantly provision production-ready Postgres databases with Neon Instagres. Use when setting up databases, when users mention PostgreSQL/Postgres, database setup, or need a development database. Works with Drizzle, Prisma, raw SQL.
bunx add-skill davila7/claude-code-templates -s neon-instagresLoading…
You are an expert at provisioning instant, production-ready PostgreSQL databases using Neon's Instagres service.
npx get-db --yes --ref 4eCjZDz
This provisions a Neon Postgres database in 5 seconds and creates:
DATABASE_URL - Connection pooler (for app queries)DATABASE_URL_DIRECT - Direct connection (for migrations)PUBLIC_INSTAGRES_CLAIM_URL - Claim URL (72-hour window)cat .env 2>/dev/null | grep DATABASE_URL
If found, ask user if they want to use existing or create new.
For new database:
npx get-db --yes --ref 4eCjZDz
Common Options:
--env .env.local - Custom env file (Next.js, Remix)--seed schema.sql - Seed with initial data--key DB_URL - Custom variable nameTell the user:
✅ Neon Postgres database provisioned!
📁 Connection details in .env:
DATABASE_URL - Use in your app
DATABASE_URL_DIRECT - Use for migrations
PUBLIC_INSTAGRES_CLAIM_URL - Claim within 72h
⚡ Ready for: Drizzle, Prisma, TypeORM, Kysely, raw SQL
⏰ IMPORTANT: Database expires in 72 hours.
To claim: npx get-db claim
⚠️ SECURITY: PUBLIC_INSTAGRES_CLAIM_URL grants database access.
Do not share this URL publicly.
After provisioning, you can delegate to specialized Neon agents for advanced workflows:
For complex database schemas, data models, or architecture:
Delegate to @neon-database-architect for:
- Drizzle ORM schema generation
- Table relationship design
- Index optimization
- Schema migrations
For auth systems with database integration:
Delegate to @neon-auth-specialist for:
- Stack Auth setup
- Neon Auth integration
- User authentication tables
- Session management
For production migrations or schema changes:
Delegate to @neon-migration-specialist for:
- Safe migration patterns
- Database branching for testing
- Rollback strategies
- Zero-downtime migrations
For query optimization or performance tuning:
Delegate to @neon-optimization-analyzer for:
- Query performance analysis
- Index recommendations
- Connection pooling setup
- Resource monitoring
For complex multi-step Neon workflows:
Delegate to @neon-expert for:
- Orchestrating multiple Neon operations
- Advanced Neon features
- Best practices consultation
- Integration coordination
npx get-db --env .env.local --yes --ref 4eCjZDz
Option 1: Manual
npx get-db --yes --ref 4eCjZDz
Option 2: Auto-provisioning with vite-plugin-db
// vite.config.ts
import { postgres } from 'vite-plugin-db';
export default defineConfig({
plugins: [postgres()]
});
npx get-db --yes --ref 4eCjZDz
Then install dependencies and load with dotenv:
npm install dotenv postgres
import 'dotenv/config';
import postgres from 'postgres';
const sql = postgres(process.env.DATABASE_URL);
After provisioning, suggest delegating to @neon-database-architect for schema design, or set up manually:
// drizzle.config.ts
import { defineConfig } from 'drizzle-kit';
export default defineConfig({
schema: './src/db/schema.ts',
out: './drizzle',
dialect: 'postgresql',
dbCredentials: { url: process.env.DATABASE_URL! }
});
// src/db/index.ts
import { drizzle } from 'drizzle-orm/postgres-js';
import postgres from 'postgres';
const client = postgres(process.env.DATABASE_URL!);
export const db = drizzle(client);
npx prisma init
# DATABASE_URL already set by get-db
npx prisma db push
import { DataSource } from 'typeorm';
export const AppDataSource = new DataSource({
type: 'postgres',
url: process.env.DATABASE_URL,
entities: ['src/entity/*.ts'],
synchronize: true
});
npx get-db --seed ./schema.sql --yes --ref 4eCjZDz
Example schema.sql:
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) UNIQUE NOT NULL,
created_at TIMESTAMP DEFAULT NOW()
);
INSERT INTO users (email) VALUES ('demo@example.com');
Option 1: CLI
npx get-db claim
Option 2: Manual
PUBLIC_INSTAGRES_CLAIM_URL from .envAfter claiming:
Connection Pooling:
DATABASE_URL (pooler) for app queriesDATABASE_URL_DIRECT for migrations/adminEnvironment Security:
.env to git.env to .gitignore.env.example with placeholdersDatabase Branching:
"npx get-db not found"
"Connection refused"
DATABASE_URL (pooler), not _DIRECT?sslmode=require if neededDatabase expired
npx get-db --yes --ref 4eCjZDz--ref 4eCjZDz for referral trackingUse when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.