prisma-compute

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

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

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 workspaces, loopback-only host binding, port mismatches, and framework-specific build outputs. This Skill guides agents through the correct commands, config, and troubleshooting steps so deployments succeed on the first attempts. ## Core Features & Use Cases - Deployment workflows: Create or update prisma.compute.ts with defineComputeConfig, run @prisma/cli app deploy, and verify the public deployment URL. - Framework readiness checks: Validate deploy readiness for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, Elysia, and custom prebuilt artifacts, including 0.0.0.0 host binding and PORT handling. - Auth and workspace management: Handle PRISMA_SERVICE_TOKEN, multiple stored OAuth workspaces, and non-interactive CI deploys. - Use Case: A user asks to deploy a Hono API in a Turborepo to Prisma Compute. The Skill inspects the repo, writes a multi-app prisma.compute.ts, verifies auth with auth workspace list --json, deploys with --json --no-interactive, and curls the public 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 the Prisma Platform CLI with `bunx @prisma/cli@latest app deploy`, or the generated `compute:deploy` script if the project has one. Add flags like `--framework`, `--entry`, `--http-port`, and `--env`, and verify the public deployment URL afterward.

Which frameworks can deploy to Prisma Compute?

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 via the custom framework.

Why is my Prisma Compute deployment unreachable after a successful deploy?

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 the port, so a loopback-only listener can appear ready while public ingress cannot reach it.

Does prisma.compute.ts replace deploy flags?

No. `prisma.compute.ts` stores reusable app defaults like framework, entry, httpPort, root, and env files, but explicit flags such as `--framework`, `--http-port`, and `--env` override config values. Project, branch, and production intent always come from flags or environment, never the config.

How do I authenticate Prisma Compute deploys in CI?

Set a non-empty `PRISMA_SERVICE_TOKEN` environment variable, which takes precedence over stored OAuth workspaces. Combine it with `--json --no-interactive` flags, and never print the token value in logs.

Do Prisma Compute deploys 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 project's own Prisma migration scripts separately.