[gregory-boch-prisma]

I'm a PM at Prisma. Prisma's Marketplace listing is Prisma Postgres (vercel integration add prisma), but three skills call it "Prisma", which reads as Prisma ORM, and one points Prisma ORM users at Neon only.

Summary

• create-a-backend: the Marketplace Postgres list said "Prisma", which reads as the ORM. Now "Prisma Postgres", the product name on the listing.
• vercel-storage chainTo message for @prisma/client: said "Neon Postgres integration with Prisma". That import only means the app uses Prisma ORM, which runs on any Postgres, so the message now names the Marketplace Postgres providers (Neon, Supabase, AWS Aurora, Nile, Prisma Postgres). Pattern and skipIfFileContains are unchanged.
• marketplace chainTo message for storage packages: the list said "Prisma"; now "Prisma Postgres". Pattern unchanged.
• vercel-storage "Prisma ORM (Marketplace Native)" section: renamed to "Prisma Postgres (Marketplace Native)". Dropped the claim that pooling comes from Prisma Accelerate: Prisma Postgres pools with PgBouncer on every plan, and Accelerate retires on 2026-12-01 (docs). The example now uses the DATABASE_URL the integration sets, with pg, since any Postgres client works (Prisma Postgres on Vercel).

The decision-matrix row "Type-safe ORM with migrations | Prisma | @prisma/client" is about the ORM and stays as is.

Validation

• npx --yes bun run test (typecheck + suite): 1079 pass, 0 fail.
• npx --yes bun run scripts/validate.ts: all checks passed.
• bun run build:skills:check and bun run build:from-skills:check: no drift.
• git diff --check: clean.
• No line overlap with the open PRs that touch these files: [skills] Sync vercel-storage with current docs #330 (Turso section only), [skills] add a Vercel Daemons skill #344 (create-a-backend, hunks above the provider list), Scope skill routing and setup to the selected architecture #333, Fix react-best-practices description and broken skill examples #325 and [skills] Sync marketplace with current docs #319 (marketplace, hunks below the chainTo message).

---

Update (@molebox)

Merged main and revised the Prisma Postgres section so it matches Prisma's own Vercel guide (https://www.prisma.io/docs/guides/postgres/vercel), Prisma's connection-pooling docs, and Vercel's Fluid compute pooling guide.

• Environment variables: the integration sets DATABASE_URL, POSTGRES_URL and PRISMA_DATABASE_URL. All three hold the direct connection string (db.prisma.io), not the pooled one, so "built-in connection pooling" via DATABASE_URL was removed. The section explains the direct-connection caps (10 on Free and Starter, 5 reserved) and how to add the pooled string (pooled.db.prisma.io) yourself under a new name (example: DATABASE_URL_POOLED). It also says to keep DATABASE_URL for migrations, and notes that PRISMA_DATABASE_URL can still hold an Accelerate URL on older databases.
• Pool setup: replaced max: 1 with Vercel's documented pattern: a module-scope Pool plus attachDatabasePool(pool) from @vercel/functions (https://vercel.com/kb/guide/connection-pooling-with-functions). Type-checked against pg@8.23.1, @types/pg and @vercel/functions@3.10.1.
• Provider order: restored the original order (Neon, Supabase, AWS/Aurora, Nile, Prisma Postgres) and kept the product-name correction ("Prisma Postgres", per the "Prisma Postgres for Vercel" listing).

Checks: build:*:check, validate, and bun run test (1119 pass). FYI @gregory-boch-prisma: the node-postgres snippet on the Prisma Marketplace listing still uses DATABASE_URL with max: 1, which contradicts Prisma's own guide.

---

Update (@gregory-boch-prisma, 2026-10-20): signed commits

The branch is now a single commit signed by GitHub (9d245ac), on main at 0db4408. The changed lines match the approved head 7c1a446 exactly, and @molebox is credited as co-author. Re-run on the new head: bun run test 1268 pass, 0 fail; validate and both build:*:check clean.

Thanks for the pooled-string fix, and for the heads-up on the node-postgres snippet on our listing.

🤖 Generated with Claude Code