prisma-compute

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

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sristigupta04/Airbnb-app --skill prisma-compute-sristigupta04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/sristigupta04/Airbnb-app/tree/main/Full-stack/.agents/skills/prisma-compute
Command: npx skills add https://github.com/sristigupta04/Airbnb-app --skill prisma-compute-sristigupta04

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 workflow so apps actually become reachable on their public URL. ## 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 Compute config: Author prisma.compute.ts with defineComputeConfig for single apps, monorepos, multi-app targets, custom build artifacts, regions, and env inputs. - Framework readiness: Validate deploy requirements for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun/Elysia, SvelteKit, and Turborepo, including host/port binding rules. - Use Case: A user merges a Hono API into a monorepo and asks to deploy a preview branch. The Skill selects the apps.api target, aligns --branch across deploy, database, and env commands, deploys with --json --no-interactive, and verifies the public deployment URL. ## Quick Start Ask the agent to deploy your existing app to Prisma Compute, for example: deploy this Hono app to Prisma Compute on the preview 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 generated compute:deploy script if the project has one, otherwise run bunx @prisma/cli@latest app deploy with the appropriate --framework, --http-port, and --env flags. Do not run create-prisma inside an existing app just to deploy it.

Which frameworks can deploy to Prisma Compute?

The CLI deploy supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. SvelteKit has no dedicated deploy key and must use a Node adapter artifact via the custom framework or a Bun entrypoint.

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 that the port is listening, so a loopback-only server 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, but explicit flags such as --framework, --region, 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, and run deploys with --json --no-interactive. Never print the token value, and unset it if you need to switch local OAuth workspaces.

Does a Prisma Compute deploy 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 app's own Prisma migration scripts separately after setup.