prisma-compute

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

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/PrimotionStudio/turbo-repo-is-cool --skill prisma-compute-primotionstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/PrimotionStudio/turbo-repo-is-cool/tree/main/packages/db/.agents/skills/prisma-compute
Command: npx skills add https://github.com/PrimotionStudio/turbo-repo-is-cool --skill prisma-compute-primotionstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying TypeScript apps to Prisma Compute involves many failure points: wrong CLI commands, missing host/port binding, misconfigured prisma.compute.ts files, ambiguous auth workspaces, and framework-specific build requirements. This Skill guides agents through the entire Prisma Compute lifecycle so deployments succeed on the first attempt. ## Core Features & Use Cases - Deployment Guidance: Covers @prisma/cli app deploy, generated compute:deploy scripts, preview branch deploys, --no-promote candidate builds, and production promotion. - Typed Config Authoring: Explains prisma.compute.ts with defineComputeConfig, single-app vs multi-app apps targets, monorepo roots, and flag-over-config precedence. - Framework Readiness: Details deploy requirements for Next.js standalone output, Hono, NestJS, Nuxt, Astro, TanStack Start, Bun/Elysia entrypoints, and custom prebuilt artifacts. - Use Case: You have a Turborepo with a Hono API and a Next.js web app. The Skill helps you write a root prisma.compute.ts with two apps targets, bind servers to 0.0.0.0, and deploy each target with the correct branch and env scope. ## Quick Start Ask the agent to deploy your existing Hono 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 app to Prisma Compute?

Use the generated `compute:deploy` script if the project has one, otherwise run `bunx @prisma/cli@latest app deploy` with the appropriate `--framework`, `--http-port`, and `--env` flags. Verify the public deployment URL afterward rather than trusting local checks.

Which frameworks does Prisma Compute deploy support?

The deploy CLI supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Elysia deploys through the bun key with an explicit entrypoint, while SvelteKit has no dedicated key and needs a custom Node artifact.

Why is my deployed Prisma Compute app unreachable?

The most common cause is binding the server to localhost or 127.0.0.1 instead of 0.0.0.0, since Compute readiness only checks the listening port. Also confirm the app listens on the deployed HTTP port, typically by reading process.env.PORT.

Do I need a prisma.compute.ts file to deploy?

No, a simple single app can deploy with explicit `app deploy` flags alone. The config file is useful for reusable defaults and is the practical way to declare multiple app targets and roots in monorepos.

How does PRISMA_SERVICE_TOKEN affect CLI authentication?

A non-empty PRISMA_SERVICE_TOKEN becomes the active auth source and overrides stored OAuth workspace sessions, so workspace switching is unavailable while it is set. If the variable is set but empty, the CLI fails instead of falling back to local OAuth credentials.

Does deploying to Prisma Compute run database migrations?

No, deploys never run migrations, seed data, or schema push. Create databases with `database create`, manage env vars with project env commands, and run your app's own Prisma migration scripts separately.