prisma-compute

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

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/brillianodhiya/VisionScript --skill prisma-compute-brillianodhiya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/brillianodhiya/VisionScript/tree/main/.agents/skills/prisma-compute
Command: npx skills add https://github.com/brillianodhiya/VisionScript --skill prisma-compute-brillianodhiya

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 actually work. ## Core Features & Use Cases - Verified CLI Surface: Runs help output and a verification script before assuming commands, flags, or package names for @prisma/cli and 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. - Operations and Troubleshooting: Handles auth with PRISMA_SERVICE_TOKEN, branch-scoped env vars and databases, logs, domains, promotions, and public-URL smoke testing. - Use Case: A user asks to deploy an existing Hono API to Prisma Compute; the Skill verifies the current CLI, checks host/port binding, deploys with JSON output, and smoke-tests the public URL. ## Quick Start Ask the agent to deploy your existing TypeScript app to Prisma Compute and verify the public deployment 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 flags like --json, --no-interactive, --env .env, and --prod --yes for production. Verify current help output first since the CLI surface is evolving.

Which frameworks does Prisma Compute app deploy support?▼

Current @prisma/cli app deploy framework keys are nextjs, hono, tanstack-start, and bun. Elysia, Nest, and custom servers deploy via --framework bun --entry, while Astro, Nuxt, and SvelteKit lack dedicated deploy keys and need a Node server artifact or SDK flow.

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 a port mismatch with --http-port. Compute readiness only checks listening ports, so a loopback-only 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; pass --deploy explicitly.

How do I authenticate Prisma Compute deploys in CI?▼

Set the PRISMA_SERVICE_TOKEN environment variable with a valid workspace service token, which @prisma/cli accepts before falling back to stored browser-login credentials. Never print the token value, and note that older SDK examples using PRISMA_API_TOKEN do not apply to the CLI.

Does the compute:deploy script run database migrations?▼

No. The generated compute:deploy script redeploys app code and env from .env only; it does not create projects or databases, run migrations, or seed data. Run the project's Prisma migration scripts separately before or after deploying.