prisma-compute

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

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/singhaditya73/Naviq --skill prisma-compute-singhaditya73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/singhaditya73/Naviq/tree/main/packages/db/.agents/skills/prisma-compute
Command: npx skills add https://github.com/singhaditya73/Naviq --skill prisma-compute-singhaditya73

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 moving parts: typed config files, framework-specific build outputs, workspace auth, branch-scoped env vars, and host/port binding rules. This Skill guides agents through the entire Prisma Compute lifecycle so deployments succeed without misconfigured frameworks, loopback-only servers, or wrong workspace credentials. ## 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, manage single-app or multi-app apps targets, and understand flag-over-config precedence. - Framework readiness: Validate 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. Use this Skill to write a root prisma.compute.ts with two apps targets, then run bunx @prisma/cli@latest app deploy api --branch feature/foo --json and verify the public deployment URL. ## Quick Start Ask the agent to deploy your existing app to Prisma Compute, for example: "Deploy my Hono API in apps/api to Prisma Compute on the current branch 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 the Prisma Platform CLI with `bunx @prisma/cli@latest app deploy`, passing flags like `--framework`, `--entry`, `--http-port`, and `--env`. If the project has a generated `compute:deploy` script or a `prisma.compute.ts` config, prefer those over reconstructing flags manually.

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

prisma.compute.ts is a typed config file using `defineComputeConfig` that stores reusable deploy defaults like framework, entrypoint, port, and env files. It is optional for simple single apps but recommended for monorepos, where an `apps` map defines one deploy target per package.

Which frameworks does Prisma Compute deploy support?

The deploy CLI supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Apps without a dedicated key, like Elysia or SvelteKit, deploy through the Bun entrypoint path or a custom prebuilt 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 via process.env.PORT or a matching `--http-port` flag.

Does Prisma Compute deploy run database migrations automatically?

No. Deploys never run migrations, seeds, or schema push, and they do not create databases automatically. Create databases with `database create`, set env vars with `project env` commands, and run your own Prisma migration scripts separately.

How do I authenticate Prisma Compute deploys in CI?

Set a non-empty PRISMA_SERVICE_TOKEN environment variable, which takes precedence over stored OAuth sessions, and run deploys with `--json --no-interactive`. Never print the token value, and unset it if you need to switch local OAuth workspaces.