feat(prisma-postgres-setup): trigger on "I need a database" and create-db

[gregory-boch-prisma]

What

prisma-postgres-setup now loads when a user needs a database and has none configured, or runs create-db, not only when they name Prisma Postgres. Three files, prisma-postgres-setup and its README entry only.

File	Change
prisma-postgres-setup/SKILL.md	description adds "I need a database", "add a Postgres database", "set up a database for this app" and create-db / npx create-db as triggers, and says the skill reuses an existing connection first and honors an explicit provider, driver, alternative ORM, or database-only choice (523 characters; the Agent Skills limit is 1024).
prisma-postgres-setup/SKILL.md	New routing row "No database yet and no provider named", placed after the v0 / Vercel Marketplace row so the Marketplace flow still wins inside v0. It offers npx create-db@latest (no account to create; deleted after 24 hours unless claimed; claiming needs a free Prisma account) or a persistent database, and asks which one when the request does not say.
prisma-postgres-setup/SKILL.md	metadata.version 2.0.0 → 2.1.0
prisma-postgres-setup/references/provisioning.md	First sentence of the create-db section: "Use create-db when the user needs a working database now and has no connection or Prisma account." The 24-hour, claim URL and Prisma-account lines stay. Both create-db links point at the canonical page.
README.md	The prisma-postgres-setup "Use when" sentence matches the new triggers.

Not touched: prisma-compute/ and provisioning.md line 10, which #31 edits. #31 bumps this skill to 2.0.1; whichever PR merges second keeps 2.1.0 (that version line is the only overlap; README and provisioning.md merge cleanly with #31).

Why

The 2.0.0 description fires only on "set up Prisma Postgres", "connect my app to Prisma Postgres", v0 or the Vercel Marketplace, and provisioning.md said to use create-db "only when a temporary, claimable development database fits the request". An agent asked "I need a database" in a project with no DATABASE_URL never reaches this skill, so it never offers create-db or a Prisma Postgres database. The new row keeps the existing order: reuse an existing connection, honor a named provider, then offer the two options.

The old docs links (/docs/postgres/introduction/npx-create-db) return a 308 to /docs/postgres/npx-create-db.

Sources (checked 2026-10-12)

• https://www.prisma.io/docs/postgres/npx-create-db: "No sign-up required to create a temporary ... database", 24 hours by default, claim URL, sign in to a Prisma account to claim, "Keep your database for free". The #claiming-your-database anchor exists.
• create-db 1.2.1 (npm latest): create and regions subcommands; --region, --interactive, --json, --env, --ttl, --copy, --quiet, --open; programmatic create() and regions() (published dist/index.d.mts).

How verified

• The repo's "Validate SKILL.md files" script, run locally with gray-matter: all skills valid; the parsed description is 523 characters and contains "I need a database" and "create-db".
• git diff origin/main --stat: 3 files, nothing under prisma-compute/.
• git merge-tree against fix(prisma-compute): teach the Composer deploy surface of the Prisma 8 CLI #31's head (fc11ec9): one conflict, the metadata.version line.

🤖 Generated with Claude Code

[gregory-boch-prisma]

@prisma-gizmo review