AutoGineer
Generated banner for Prisma Postgres Setup
Generated logo for Prisma Postgres Setup

Prisma Postgres Setup

PrismaOfficialCreated by prisma

  • Skill
  • Workflow
  • Software development
  • MIT
  • Low risk
Download ZIP

From the author

Obtain or reuse a Prisma Postgres database and connect an application. Use when the user needs a database and has none configured ("I need a database", "add a Postgres database", "set up a database for this app"), runs or mentions `create-db` or `npx create-db`, or asks to set up or connect Prisma Postgres, including in v0 and the Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; reuses an existing connection first and honors an explicit provider, driver, alternative ORM, or database-only choice.
— the description by prisma

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to managing database connections for applications. It prioritizes reusing existing database resources before provisioning new ones. It handles various environments, including Vercel Marketplace and v0, and supports both persistent database setup and temporary development databases via create-db. The skill ensures secure handling of environment variables and delegates ORM-specific configuration to dedicated tools.

What it does

  • Inspects existing project configurations to identify current database or ORM setups.
  • Reuses existing database connections when available to avoid redundant provisioning.
  • Provisions new persistent databases using authenticated CLI, Console, or Management API tools.
  • Sets up temporary development databases with automatic expiry using create-db.
  • Configures application environment variables securely for database connectivity.
  • Verifies database connectivity by running a read-only query through the application's ORM or driver.

When to use it

  • When a user needs to add a Postgres database to an application that currently has none.
  • When a user explicitly requests to set up or connect a Prisma Postgres database.
  • When working within v0 or Vercel Marketplace environments requiring native integration.
  • When a user needs a temporary database for development purposes.

Advantages

  • Prevents accidental duplicate database creation by checking existing resources first.
  • Maintains security by keeping credentials out of source code and chat logs.
  • Integrates seamlessly with existing ORM workflows by delegating configuration.
  • Supports diverse deployment scenarios from local development to cloud platforms.

Usage examples

“I need a database for this app.”
The agent inspects the project for existing connections, then offers to provision a new database or use create-db if no account is available.
“Set up a Postgres database for my project.”
The agent identifies the environment, checks for existing credentials, and proceeds to provision a persistent database, storing the connection string in the project's secrets.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/prisma/prisma-postgres-setup/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip prisma-postgres-setup.zip -d .agents/skills

Documentation by prisma

Prisma Postgres setup

Connect the intended database, then verify it from the application. Keep provisioning separate from ORM configuration so an existing database is reused.

1. Inspect the project

Check the user's requested ORM or driver, installed packages, database connection, and environment-loading files. Check secret presence without printing values.

  • Honor explicit choices such as Drizzle, pg, or database-only setup.

  • For query or schema work in an already configured app, use its version-matched ORM guidance; do not restart setup.

2. Reuse or obtain a database

SituationAction
Existing connection or connected integrationVerify its project, database, and environment; reuse it.
v0, Vercel Marketplace, or a Vercel projectRead Marketplace setup and use the native integration flow.
No database yet and no provider namedOffer npx create-db@latest for a working database now with no account (it is deleted after 24 hours unless claimed, and claiming needs a free Prisma account; read the create-db section in provisioning), or a persistent database through provisioning. Ask which one when the request does not say.
Standalone persistent databaseRead provisioning; use an authenticated CLI, MCP tool, Console, or Management API.
Temporary development database requestedRead the create-db section in provisioning, including expiry and claiming.

Resolve the workspace, project, and region before creation. If several resources fit, ask which one to use. If provisioning is blocked by permissions or quota, report the blocker; do not delete another resource or switch workspaces to get around it.

3. Connect the application

Use the connection appropriate to the chosen driver and runtime. Store it in the project's secret environment configuration, never source code or chat. Preserve unrelated entries, update the intended variable once, and ensure local secret files are ignored by Git.

Application processes and CLI commands may load different environment files. For example, a framework may load .env.development.local while a shell command does not. A variable missing from the shell does not mean the database is missing: load the intended file for that command without displaying credentials, and do not provision another database.

4. Configure the ORM and verify

For Prisma ORM setup, read prisma-orm-setup/SKILL.md directly, or load the installed prisma-orm-setup skill when the host resolves sibling skills by name. It owns ORM version selection and configuration. If that handoff is unavailable, report it.

For an explicitly selected alternative, keep that ORM or driver and use its documented setup. For database-only setup, stop after verifying connectivity.

Run a read-only query against the intended database through the application's chosen ORM or driver. Report what was connected, the selected ORM/version, and the query result without secrets. If any step is blocked or untested, say so instead of claiming setup is complete.

For Studio, SDK integrations, or database operations beyond initial setup, read operations.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
prisma
Publisher
Prisma (Official)
Source
prisma/skills · prisma-postgres-setup · commit 8ea289b
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by prisma or Prisma.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download prisma-postgres-setup.zip