80 prisma

prisma-postgres-setup Skill

获取或复用 Prisma Postgres 数据库并连接应用。适用于"set up Prisma Postgres"、"connect my app to Prisma Postgres",或在 v0 和 Vercel Marketplace 中设置 Prisma Postgres。将 Prisma ORM 配置交给 prisma-orm-setup;若用户明确指定驱动、其他 ORM 或仅数据库方案,则以用户选择为准。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

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

| 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.

配合站内内容