prisma-compute

Deploys TypeScript applications to Prisma Compute using the Prisma Platform CLI.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarixHine/uni-chem --skill prisma-compute-narixhine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/NarixHine/uni-chem/tree/main/.agents/skills/prisma-compute
Command: npx skills add https://github.com/NarixHine/uni-chem --skill prisma-compute-narixhine

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 failure points: wrong CLI package, missing typed config, loopback-only host binding, port mismatches, ambiguous workspace auth, and framework-specific build output requirements. This Skill guides agents through the correct commands, config shapes, and troubleshooting steps so deployments succeed on the first attempt. ## Core Features & Use Cases - Deploy Command Guidance: Covers @prisma/cli app deploy, generated compute:deploy scripts, JSON/non-interactive output, and public URL verification. - Typed Config Authoring: Explains prisma.compute.ts with defineComputeConfig, single-app vs multi-app apps targets, monorepo roots, and flag-over-config precedence. - Framework Readiness: Details deploy requirements for Next.js standalone output, Hono, NestJS, Nuxt, Astro, TanStack Start, Bun/Elysia entrypoints, and custom prebuilt artifacts. - Auth and Operations: Handles multi-workspace OAuth switching, PRISMA_SERVICE_TOKEN precedence, build logs vs runtime logs, domains, promote/rollback, and branch-scoped env and databases. - Use Case: A developer has a Hono API in a monorepo and asks the agent to deploy a preview branch. The Skill directs the agent to create a prisma.compute.ts with an apps target, align --branch across deploy, database, and env commands, bind the server to 0.0.0.0:8080, and verify 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 feature/login 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 flags like --framework, --http-port, and --env. Add --json --no-interactive for agent-driven deploys and verify the public deployment URL afterward.

What is prisma.compute.ts and when do I need it?▼

prisma.compute.ts is the typed Compute config using defineComputeConfig from @prisma/compute-sdk/config. It is optional for simple single-app deploys but recommended for reusable defaults and required in practice for monorepos with multiple apps targets.

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 key and must deploy through a custom prebuilt artifact or a Bun server entrypoint.

Why is my deployed app unreachable even though the deploy succeeded?▼

The most common cause is binding the server to localhost or 127.0.0.1 instead of 0.0.0.0, since Compute readiness only checks the listening port. Also confirm the app listens on the deployed HTTP port, reading process.env.PORT or matching --http-port.

How does PRISMA_SERVICE_TOKEN interact with workspace login?▼

A non-empty PRISMA_SERVICE_TOKEN is the active auth source and overrides stored OAuth workspaces, so auth workspace use is unavailable while it is set. If the variable is set but empty, the CLI fails instead of falling back to local OAuth credentials.

Does deploying to Prisma Compute run database migrations?▼

No. Deploys never run migrations, seed data, or schema push, and prisma.compute.ts does not declare databases. Create databases with database create, set env vars with project env commands, and run your own migration scripts separately.