prisma-compute

Deploy and manage TypeScript apps on Prisma Compute using the Prisma Platform CLI.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Rashidrxq/SalesOrder-ERP-REMEX --skill prisma-compute-rashidrxq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/Rashidrxq/SalesOrder-ERP-REMEX/tree/main/sales_order/.windsurf/skills/prisma-compute
Command: npx skills add https://github.com/Rashidrxq/SalesOrder-ERP-REMEX --skill prisma-compute-rashidrxq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @prisma/cli, create-prisma, @prisma/compute-sdk, @prisma/management-api-sdk, and includes references (resource) components.

What problem does it solve? Deploying TypeScript apps to Prisma Compute involves many failure points: wrong CLI package, missing auth workspace selection, loopback-only host binding, port mismatches, and misconfigured prisma.compute.ts files. This Skill guides agents through the correct deploy, config, and troubleshooting paths so apps actually become reachable in production. ## Core Features & Use Cases - CLI-Guided Deployment: Uses @prisma/cli app deploy, create-prisma, and generated compute:deploy scripts with verified command syntax and JSON output for automation. - Typed Compute Config: Creates and validates prisma.compute.ts with defineComputeConfig for single apps, monorepos, multi-app targets, and custom build artifacts. - Framework Readiness Checks: Covers Next.js standalone output, Hono, NestJS, Nuxt, Astro, TanStack Start, Bun/Elysia entrypoints, and custom prebuilt artifacts, including host/port binding rules. - Use Case: A user has a Hono API that deploys successfully but is unreachable publicly. The Skill diagnoses the hard-coded localhost binding, fixes it to 0.0.0.0 with the correct --http-port, redeploys, and verifies the public URL. ## Quick Start Ask the agent to deploy your existing TypeScript app to Prisma Compute and verify the public deployment URL.

Frequently Asked Questions about prisma-compute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an existing TypeScript app to Prisma Compute?▼

Use `bunx @prisma/cli@latest app deploy` with flags like `--framework`, `--entry`, `--http-port`, and `--env`, or run the generated `compute:deploy` script if the project has one. Do not run `create-prisma` inside an existing app just to deploy it.

Which frameworks does Prisma Compute deploy support?▼

The deploy CLI supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. SvelteKit has no dedicated deploy key and must use a Node adapter artifact via the custom framework or a Bun entrypoint.

Why is my Prisma Compute deployment unreachable after a successful deploy?▼

The most common cause is binding the server to localhost or 127.0.0.1 instead of 0.0.0.0, or listening on the wrong port. Compute readiness only checks that the port is listening, so a loopback-only server can appear ready while public ingress cannot reach it.

How do I switch between multiple Prisma workspaces in the CLI?▼

Run `auth workspace list --json` to see stored OAuth sessions, then `auth workspace use <workspace-id>` to switch explicitly. While `PRISMA_SERVICE_TOKEN` is set, workspace switching is unavailable because the service token is the active auth source.

Does prisma.compute.ts replace prisma.config.ts?▼

No. `prisma.compute.ts` holds Compute deploy defaults like framework, entry, httpPort, and env files, while `prisma.config.ts` belongs to Prisma ORM. Never put Compute deploy settings in `prisma.config.ts` or secrets in `prisma.compute.ts`.

Why does my Next.js deploy fail with missing standalone output?▼

Next.js Compute deploys require `output: "standalone"` in `next.config.ts` so the build produces a standalone `server.js`. Add that setting, rebuild, and redeploy; do not pass `--entry` with the nextjs framework.