prisma-compute

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

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/jpmartirez/kilatis --skill prisma-compute-jpmartirez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/jpmartirez/kilatis/tree/main/frontend/.windsurf/skills/prisma-compute
Command: npx skills add https://github.com/jpmartirez/kilatis --skill prisma-compute-jpmartirez

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 typed config, localhost-only port binding, wrong branch or env scope, and framework-specific build requirements. This Skill guides agents through the entire Prisma Compute lifecycle so deployments succeed on the first attempt. ## Core Features & Use Cases - Deployment Guidance: Covers @prisma/cli app deploy, generated compute:deploy scripts, non-interactive JSON deploys, --no-promote candidate builds, and production promotion. - Typed Config Authoring: Explains prisma.compute.ts with defineComputeConfig, single-app vs monorepo apps targets, build blocks, env inputs, and flag 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 CI auth, build vs runtime logs, custom domains, and troubleshooting. - Use Case: A developer asks why their deployed Hono API is unreachable; the Skill diagnoses the hard-coded localhost binding and prescribes 0.0.0.0 with the correct --http-port. ## Quick Start Ask the agent to deploy your existing app to Prisma Compute, for example: deploy this Hono API to Prisma Compute on port 8080 using my .env file.

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. Verify the public deployment URL afterward rather than trusting local checks.

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

prisma.compute.ts is a typed config file using defineComputeConfig that stores reusable deploy defaults like framework, entry, httpPort, and env. It is optional for single apps but recommended for monorepos with multiple app targets.

Which frameworks can deploy to Prisma Compute?

The CLI deploy supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Next.js requires standalone output, TanStack Start and Nuxt need Nitro node server output, and SvelteKit has no dedicated deploy key.

Why is my deployed Prisma Compute app unreachable?

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

How do I authenticate Prisma CLI deploys in CI?

Set the PRISMA_SERVICE_TOKEN environment variable with a workspace service token; a non-empty token takes precedence over stored OAuth sessions. Never print the token, and use --json --no-interactive flags for non-interactive deploys.

Does 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 migration scripts separately after setup.