fix(prisma-compute): teach the Composer deploy surface of the Prisma 8 CLI

[sorenbs]

Summary

prisma-compute (1.5.1) taught the Compute CLI from before Composer: bunx @prisma/cli@latest app deploy, prisma.compute.ts / defineComputeConfig, compute:deploy, build logs, app logs. Against prisma / @prisma/cli 8.0.0-rc.21, app deploy returns CLI.UNKNOWN_COMMAND, so an agent following the skill ran commands that no longer exist.

This rewrites the skill (2.0.0) for the surface that exists today:

• Deploys go through Prisma Composer: module.ts, a service.ts per server, the composer section of prisma.config.ts, then npx prisma dev module.ts / npx prisma deploy module.ts / --stage <name>.
• Deploy on push: prisma git connect plus a workflow running prisma/cloud-deploy-action.
• Operations: service (logs, versions, rollback with --to/--confirm, domains), project env, postgres, bucket.
• A "Removed surface" table maps every old command to its replacement.
• Package skills: the skill defers to the version-matched skills that prisma and @prisma/composer ship (prisma skills sync) for API detail.

Files

• prisma-compute/SKILL.md: rewritten, version 2.0.0.
• Deleted: references/app-deploy-cli.md and references/compute-config.md, which only described the removed surface.
• Rewritten and renamed:
  • frameworks.md → app-framework-builds.md
  • create-prisma.md → automation-create-prisma.md
  • sdk-api.md → automation-rest-api.md
  • troubleshooting.md → debug-deploy-failures.md
• New references: cli-command-map.md, app-composer-setup.md, runtime-requirements.md, deploy-cli-and-ci.md, deploy-on-push.md, ops-services-and-config.md.
• README.md: the prisma-compute entry.
• prisma-postgres-setup/references/provisioning.md: pointed at the removed database group; it now says postgres (skill bumped to 2.0.1).

How it was verified

• Commands: every command and flag was checked against --help from prisma and @prisma/cli 8.0.0-rc.21, @prisma/composer and @prisma/composer-prisma-cloud 0.28.0, @prisma/compute, and create-prisma 0.14.1, plus the CLI source for consent tokens, targeting and the .prisma/local.json link.
• Removed commands: each one in the table was run with --json --no-interactive (no network) to confirm it returns CLI.UNKNOWN_COMMAND.
• Code samples: the example app and control-API snippets type-check, and the bundle builds with bun build.
• REST paths: checked against the live spec at https://api.prisma.io/v1/doc.
• Not run: nothing signs in, deploys, or creates remote resources.
• Repo check: validate-skills passes locally.

Not changed

prisma-cli/SKILL.md still calls @prisma/cli a "public-beta Platform package". It already routes Compute work to prisma-compute and points at no removed command, and its version is pinned to the ORM release.

Found while reviewing the Prisma Compute GA blog post (prisma/web#8433); listed with the other follow-ups in the prisma/web follow-up PR.

🤖 Generated with Claude Code

[sampolahtinen]

prisma-postgres-setup looks great and these changes should not break Vercel marketplace discovery.