About prisma-postgres-setup
prisma-postgres-setup is a skill for setting up Prisma Postgres in an application. It guides developers through reusing or obtaining a database, configuring the chosen ORM or driver, and verifying connectivity without exposing secrets.
Key features
- 01Inspect project and database configuration
- 02Reuse or provision a database
- 03Configure secure connection settings
- 04Set up ORM or selected driver
- 05Verify connectivity with a read-only query
Use cases
- 01Connect an application to an existing database
- 02Provision a temporary or persistent database
- 03Set up database-only access without ORM changes
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/prisma-postgres-setupin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/operations.mdprovisioning.mdvercel-marketplace.mdDetails
From the project READMEPrisma 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
| Situation | Action |
|---|---|
| Existing connection or connected integration | Verify its project, database, and environment; reuse it. |
| v0, Vercel Marketplace, or a Vercel project | Read Marketplace setup and use the native integration flow. |
| No database yet and no provider named | Offer 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 database | Read provisioning; use an authenticated CLI, MCP tool, Console, or Management API. |
| Temporary development database requested | Read 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.