prisma-compute

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

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/vasuguptadot-jpg/Life-xp- --skill prisma-compute-vasuguptadot-jpg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/vasuguptadot-jpg/Life-xp-/tree/main/attached_assets/LifeXP-Complete/apps/api/.agents/skills/prisma-compute
Command: npx skills add https://github.com/vasuguptadot-jpg/Life-xp- --skill prisma-compute-vasuguptadot-jpg

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 authentication, branch-scoped env vars, and host/port binding rules. This Skill guides an AI agent through the entire Prisma Compute lifecycle so deployments succeed on the first attempt instead of failing on misconfigured ports, missing standalone output, or wrong workspace auth. ## 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 management: Author and validate prisma.compute.ts with defineComputeConfig for single apps, monorepos, and multi-app targets. - Framework readiness checks: Verify deploy requirements for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, Elysia, and custom prebuilt artifacts, including 0.0.0.0 host binding and correct HTTP port. - Auth and operations: Manage multiple OAuth workspaces, PRISMA_SERVICE_TOKEN auth, branch-scoped env vars, databases, build logs, and custom domains. - Use Case: You have a Hono API in a Turborepo monorepo. The Skill writes a root prisma.compute.ts with an apps.api target, verifies the server binds to 0.0.0.0:8080, and runs app deploy api --json --no-interactive with the correct branch env. ## 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. 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 a typed config file using `defineComputeConfig` that stores reusable deploy defaults like framework, entrypoint, port, and env files. It is optional for single apps but recommended for monorepos and multi-app repositories using the `apps` key.

Which frameworks does Prisma Compute deploy support?▼

The deploy CLI supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Frameworks without a dedicated key, like SvelteKit or Elysia, deploy through the bun entrypoint path or a custom prebuilt 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, 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 authenticate Prisma CLI deploys in CI?▼

Set the `PRISMA_SERVICE_TOKEN` environment variable with a workspace service token and run deploys with `--json --no-interactive`. A non-empty service token takes precedence over local OAuth workspaces, and an empty value causes the CLI to fail rather than fall back.

Does Prisma Compute deploy run database migrations?▼

No. Deploys and generated compute:deploy scripts 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 migration scripts separately.