prisma-compute

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

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/UdayPandey01/Healix --skill prisma-compute-udaypandey01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/UdayPandey01/Healix/tree/main/core/.agents/skills/prisma-compute
Command: npx skills add https://github.com/UdayPandey01/Healix --skill prisma-compute-udaypandey01

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 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 on their public URL. ## Core Features & Use Cases - Deploy workflows: Covers @prisma/cli app deploy, generated compute:deploy scripts, preview branch deploys, --no-promote candidate builds, and production promotion. - Typed config authoring: Creates and validates prisma.compute.ts with defineComputeConfig, including monorepo multi-app apps targets, build settings, and env inputs. - Framework readiness: Provides per-framework requirements for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun/Elysia, custom artifacts, and Turborepo. - Use Case: A user says their Hono API deploys successfully but the public URL times out. The Skill diagnoses the hard-coded localhost binding, fixes the server to bind 0.0.0.0 on process.env.PORT, and redeploys with the correct --http-port. ## Quick Start Ask the agent to deploy your existing TypeScript app to Prisma Compute and verify the public deployment URL responds.

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 project's generated `compute:deploy` script if one exists. Do not run `create-prisma` inside an existing app just to deploy it.

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

prisma.compute.ts is the typed Compute config using defineComputeConfig from @prisma/compute-sdk/config. It is optional for single-app deploys but recommended for reusable defaults and required in practice for monorepos with multiple app targets.

Which frameworks can Prisma Compute deploy?

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

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, which passes Compute's port-based readiness check but blocks public ingress. Bind to 0.0.0.0, read process.env.PORT, and verify the public deployment URL with curl rather than a local check.

How do I authenticate Prisma CLI deploys in CI?

Set a non-empty PRISMA_SERVICE_TOKEN environment variable, which takes precedence over stored OAuth workspaces. Verify with `auth whoami`, never print the token, and use `--json --no-interactive` flags for non-interactive deploys.

Does Prisma Compute run database migrations during deploy?

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 after setup.