Prisma Compute Deployment Guide
Prisma Compute deployment guide — @prisma/cli, prisma.compute.ts config, framework readiness, auth, logs
- What
- Prisma Compute deployment guide — @prisma/cli, prisma.compute.ts config, framework readiness, auth, logs
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Prisma team's guide for creating, deploying, and operating apps on Prisma Compute: it walks the agent through choosing the right CLI surface (the public-beta Platform package `@prisma/cli`, binary `prisma-cli` — explicitly not the ORM `prisma` command), writing a typed `prisma.compute.ts` deploy config with `defineComputeConfig` (single `app` vs monorepo `apps`, targets, entrypoints, regions), evaluating framework deploy readiness (nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, bun — server entrypoint required, no static-only output), and the runtime rules that bite in production (bind `0.0.0.0` not localhost, listen on `process.env.PORT`, answer within 60 seconds or the ingress returns 504). It covers the auth model too — `PRISMA_SERVICE_TOKEN` precedence over local OAuth workspaces, workspace list/switch/logout flows, project pins in `.prisma/local.json` — plus deploy operations (`--prod --yes` only on user intent, `--no-promote` build-then-verify, GitHub push-to-deploy, `build logs` vs `app logs` ids, `create-prisma` scaffolding, the `@prisma/compute-sdk`), and a built-in feedback channel for CLI crashes. By @prisma, listed here with credit to its creator. Honest caveats: the Platform CLI is public beta and Compute is newer ground than the ORM — verify command syntax with `--help` first (the skill insists on it); deploys never run migrations or seed data and never create a database per app, so wire databases and env explicitly, and never deploy with placeholder `DATABASE_URL` values or commit secrets into `prisma.compute.ts`. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Prisma Compute Deployment Guide" for me. Prisma Compute deployment guide — @prisma/cli, prisma.compute.ts config, framework readiness, auth, logs Repository: https://github.com/prisma/skills/blob/main/prisma-compute/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "prisma-compute". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.