/prisma-compute

name: prisma-compute
description: Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `prisma.compute.ts`, `defineComputeConfig`, deploying or hosting a Prisma app, `@prisma/cli app deploy`, `compute:deploy`, `create-prisma --deploy`, `PRISMA_SERVICE_TOKEN`, `auth workspace`, Compute apps/deployments/build logs/domains, `@prisma/cli agent install`, `@prisma/cli feedback`, localhost vs `0.0.0.0`, deploy port binding, or framework deploy readiness for Hono, Elysia, Next.js, TanStack Start, Astro, Nuxt, Svelte, Nest, Turborepo, or custom/prebuilt artifacts.
license: MIT
metadata:
  author: prisma
  version: "1.4.1"

Prisma Compute

Guide agents through Prisma Compute app creation, deployment, operations, and framework-specific deploy readiness.

Prisma Compute CLI Surface

Use the Prisma Platform CLI for Compute app workflows:

bunx @prisma/cli@latest app deploy --help
bunx @prisma/cli@latest app --help
bunx @prisma/cli@latest build logs --help
bunx create-prisma@latest --help

Use `@prisma/cli@latest` for Compute app deployment. Use `create-prisma@latest` for new-project scaffolding.

Send Feedback and Report CLI Issues

The CLI has a built-in feedback channel. Use it whenever a command crashes (`UNEXPECTED_ERROR`), a failure survives troubleshooting, or the user asks to send feedback to the Prisma team:

bunx @prisma/cli@latest feedback "app deploy crashed: <first error line>"
bunx @prisma/cli@latest feedback "love the deploy flow" --email you@example.com

Crash output points here on its own: `--json` crash envelopes carry the exact pre-filled command as a `recover` entry in `nextActions` (run it verbatim), and human crash output ends with a `Tell us what happened:` hint. Feedback is anonymous unless `--email` is passed and attaches only the CLI version, node version, and OS platform/arch. Never include secrets, connection URLs, or user data in the message.

Source-of-Truth Order

Use evidence in this order when deciding what to edit or run:

1. The project's generated scripts and config, especially `prisma.compute.ts`, `compute:deploy`, framework config, and `package.json`. 2. CLI help output from `create-prisma` and `@prisma/cli`. 3. Local installed package code, generated artifacts, and type definitions. 4. Official docs.

When to Apply

Use this skill for:

• Creating a new app that can deploy to Prisma Compute
• Deploying an existing TypeScript app to Prisma Compute
• Creating or updating a typed `prisma.compute.ts` deploy config
• Deciding whether a framework is Compute-ready
• Debugging `create-prisma --deploy`, `compute:deploy`, or `app deploy`
• Managing Compute app logs, deployments, environment variables, and domains, and listing platform branches (`branch list`; there are no branch create/remove commands)
• Inspecting GitHub/Console build logs and GitHub push-to-deploy status
• Running non-interactive deploys with browser auth, multiple stored workspaces, or Prisma service tokens
• Switching, selecting, listing, or logging out local Prisma Platform workspaces for `@prisma/cli`
• Installing or updating Prisma skills with `@prisma/cli agent install|update|status`
• Sending feedback or reporting unresolvable CLI failures with `@prisma/cli feedback`
• Programmatic deployments with `@prisma/compute-sdk` or Management API integrations

Decision Tree

1. Existing project deployment or redeploy: Read [`references/app-deploy-cli.md`](references/app-deploy-cli.md).

2. Typed Compute config, monorepos, deploy targets, app roots, or build/env defaults: Read [`references/compute-config.md`](references/compute-config.md).

3. Framework-specific build/runtime work: Read [`references/frameworks.md`](references/frameworks.md).

4. New project from a scaffold: Read [`references/create-prisma.md`](references/create-prisma.md).

5. Programmatic deployment, SDKs, APIs, or low-level App/Deployment concepts: Read [`references/sdk-api.md`](references/sdk-api.md).

6. Build, auth, env, deploy, or runtime failures: Read [`references/troubleshooting.md`](references/troubleshooting.md).

Rules by Priority

| Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Command verification | CRITICAL | `verify-` | | 2 | Auth and workspace selection | CRITICAL | `auth-` | | 3 | Framework readiness | CRITICAL | `framework-` | | 4 | Runtime host and port binding | CRITICAL | `runtime-` | | 5 | Typed Compute config | HIGH | `config-` | | 6 | Branch, environment, and database wiring | HIGH | `env-` | | 7 | Deploy operations | HIGH | `deploy-` | | 8 | SDK and API automation | MEDIUM | `sdk-` |

Quick Rules

1. Command Verification

• `verify-help-first` - Use CLI help output to confirm command syntax while working.
• `verify-prisma-vs-platform-cli` - Do not assume `prisma app deploy` exists in the ORM CLI; check whether the task should use `@prisma/cli`.
• `verify-generated-scripts` - Prefer the generated `compute:deploy` script when a project already has one.
• `verify-public-url` - After a real deploy, request the public deployment URL instead of trusting local or readiness-only checks.
• `verify-config-support` - Treat `prisma.compute.ts` as the typed Compute config; inspect the project's config and generated scripts before editing or deploying.
• `verify-auth-workspace-support` - Use `@prisma/cli auth workspace` commands for local workspace list/use/logout flows.

2. Auth and Workspace Selection

• `auth-source-precedence` - A non-empty `PRISMA_SERVICE_TOKEN` is the active auth source for commands and local OAuth workspaces are ignored for execution. If it is set but empty, the CLI should fail instead of falling back to stored OAuth.
• `auth-multi-workspace` - `auth login` can store OAuth sessions for multiple workspaces on the same machine. The active workspace pointer selects which stored OAuth grant normal commands use.
• `auth-list-before-switch` - Use `auth