prisma-compute

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

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/soumeningit/FlowBoard --skill prisma-compute-soumeningit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/soumeningit/FlowBoard/tree/main/packages/database/.windsurf/skills/prisma-compute
Command: npx skills add https://github.com/soumeningit/FlowBoard --skill prisma-compute-soumeningit

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 workspaces, loopback-only host binding, port mismatches, misconfigured prisma.compute.ts files, and framework-specific build requirements. This Skill guides agents through the correct commands, config shapes, and troubleshooting steps so deployments succeed on the first attempts. ## 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 config management: Author and validate prisma.compute.ts with defineComputeConfig for single apps or monorepo multi-app targets, with correct flag-over-config precedence. - Framework readiness checks: Verify deploy requirements for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, and custom artifacts, including 0.0.0.0 host binding and port alignment. - Use Case: A developer has a Hono API in a Turborepo monorepo. The Skill helps write a root prisma.compute.ts with an apps map, authenticate the right workspace, deploy the api target with --json --no-interactive, and verify the public deployment URL. ## Quick Start Ask the agent to deploy your existing app to Prisma Compute, for example: deploy my Hono API in apps/api to Prisma Compute 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 Prisma Platform CLI with bunx @prisma/cli@latest app deploy, passing flags like --framework, --entry, --http-port, and --env. If the project has a generated compute:deploy script or a prisma.compute.ts config, prefer those over reconstructing commands manually.

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, entrypoint, port, and env files. It is optional for single apps but recommended for monorepos, where an apps map defines one deploy target per package.

Which frameworks does Prisma Compute deploy support?▼

The deploy CLI supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Frameworks without a dedicated key, such as SvelteKit or Elysia, deploy through the bun entrypoint path or a custom prebuilt artifact config.

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, or listening on a port that does not match the deployed HTTP port. Read process.env.PORT, bind all interfaces, and verify the public deployment URL with curl rather than a local check.

How do I authenticate Prisma Compute 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. Run deploys with --json --no-interactive and never print the token value in logs.

Does Prisma Compute deploy run database migrations automatically?▼

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 project's own Prisma migration scripts separately after setup.