prisma-compute

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

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/team-zerolatency/cfta --skill prisma-compute-team-zerolatency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/team-zerolatency/cfta/tree/main/packages/database/.windsurf/skills/prisma-compute
Command: npx skills add https://github.com/team-zerolatency/cfta --skill prisma-compute-team-zerolatency

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 package, missing auth or workspace selection, loopback-only host binding, port mismatches, incorrect framework build output, and misconfigured prisma.compute.ts files. This Skill guides agents through the correct commands, config shapes, and troubleshooting steps so deployments succeed and are verifiable. ## Core Features & Use Cases - Deployment workflows: Create, deploy, promote, roll back, and inspect Compute apps with @prisma/cli app deploy, including non-interactive JSON output for CI and agents. - Typed config and monorepos: Author prisma.compute.ts with defineComputeConfig, define single-app or multi-app apps targets, and select targets per deploy. - Framework readiness: Validate deploy requirements for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, Elysia, and custom prebuilt artifacts, including host/port binding rules. - Use Case: A user asks to deploy a Hono API in a Turborepo to Prisma Compute. The Skill inspects the repo, writes a root prisma.compute.ts with an api target, verifies auth with auth whoami --json, deploys with --json --no-interactive, and curls the public deployment URL to confirm. ## Quick Start Ask the agent to deploy your existing app to Prisma Compute, for example: "Deploy this Hono app to Prisma Compute on port 8080 and verify the public 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 `bunx @prisma/cli@latest app deploy` with flags like `--framework`, `--http-port`, and `--env`, or run the generated `compute:deploy` script if the project has one. Add `--json --no-interactive` for agent or CI workflows, and verify the public deployment URL afterward.

What is prisma.compute.ts and when do I need it?▼

prisma.compute.ts is the typed Compute config created with `defineComputeConfig` from `@prisma/compute-sdk/config`. It is optional for simple single-app deploys but recommended for reusable defaults and monorepos, where an `apps` map declares each deploy target's root, framework, entry, port, and env.

Which frameworks does Prisma Compute deploy support?▼

The deploy CLI supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Elysia and plain servers deploy through the bun key with an explicit entrypoint, while SvelteKit needs a Node adapter artifact deployed as custom.

Why is my deployed app unreachable even though the deploy succeeded?▼

The most common cause is binding the server to localhost or 127.0.0.1 instead of 0.0.0.0, or listening on a port that does not match the deployed HTTP 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 authenticate Prisma Compute deploys in CI?▼

Set a non-empty `PRISMA_SERVICE_TOKEN` environment variable, which takes precedence over stored browser-login workspaces. Verify with `auth whoami`, never print the token, and note that workspace switching is unavailable while the token is set.

Does deploying to Prisma Compute run database migrations?▼

No. Deploys and generated `compute:deploy` scripts never run migrations, seeds, 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.