prisma-compute

Deploy and manage Prisma Compute apps using the Prisma Platform CLI.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/DimonikRV/ghost-pilot-project --skill prisma-compute-dimonikrv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/DimonikRV/ghost-pilot-project/tree/main/.agents/skills/prisma-compute
Command: npx skills add https://github.com/DimonikRV/ghost-pilot-project --skill prisma-compute-dimonikrv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Deploying TypeScript apps to Prisma Compute involves a moving CLI surface, framework-specific build requirements, and subtle runtime pitfalls like loopback-only host binding and port mismatches that make deployed apps unreachable. This Skill guides agents through verified, current commands and framework readiness checks so deployments succeed and public URLs actually respond. ## Core Features & Use Cases - Verified CLI Surface: Runs help-output checks and a verification script before assuming commands, flags, or framework keys exist in @prisma/cli or create-prisma. - Framework Deploy Readiness: Covers Next.js standalone output, Hono, TanStack Start with Nitro, Bun/Elysia/Nest entrypoints, and explains limits for Astro, Nuxt, SvelteKit, and Turborepo. - Runtime and Operations Guidance: Enforces 0.0.0.0 host binding, correct --http-port usage, branch-scoped env and database wiring, non-interactive deploys with PRISMA_SERVICE_TOKEN, and post-deploy smoke testing of public URLs. - Use Case: A user asks to deploy an existing Hono API to Prisma Compute; the Skill verifies the CLI surface, checks host/port binding, deploys with --json --no-interactive, and smoke-tests the public deployment URL. ## Quick Start Ask the agent to deploy your existing 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 app to Prisma Compute?▼

Use the generated `compute:deploy` script if the project has one, otherwise run `@prisma/cli app deploy` after verifying current help output. For automation, add `--json --no-interactive` and pass `--env .env` with real production values.

Which frameworks can deploy to Prisma Compute?▼

Current `@prisma/cli app deploy --framework` supports `nextjs`, `hono`, `tanstack-start`, and `bun`. Elysia, Nest, and custom servers deploy via `--framework bun --entry <path>`; Astro, Nuxt, and SvelteKit have no dedicated deploy key yet.

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

The most common cause is the server binding to `localhost` or `127.0.0.1` instead of `0.0.0.0`, or listening on a port that does not match `--http-port`. Compute readiness only checks the port, so a loopback listener can appear ready while public ingress cannot reach it.

Does create-prisma deploy every template automatically?▼

No. Only the `hono`, `elysia`, `next`, and `tanstack-start` templates have integrated `--deploy` support; `nest`, `svelte`, `astro`, `nuxt`, and `turborepo` are scaffold-only. Also, `--yes` alone skips prompts without opting into deploy—you must pass `--deploy` explicitly.

How do I run non-interactive Prisma Compute deploys in CI?▼

Set a valid `PRISMA_SERVICE_TOKEN` environment variable and run `@prisma/cli app deploy --json --no-interactive --prod --yes --env .env`. Never print the token value; older `PRISMA_API_TOKEN` naming applies only to legacy CLI or SDK examples.