# Deploy Prisma Apps on Compute

Prisma Compute deployments require correct framework, environment, and authentication settings. This skill guides configuration, deployment, verification, and troubleshooting across supported TypeScript frameworks.

## Install

```bash
npx skillstore add prisma/prisma-compute
```

## Metadata

- Status: approved
- Slug: prisma-prisma-compute
- Version: 1.4.1
- Author version: 1.4.1
- Skillstore revision: r2
- Version status: valid
- Tree hash: 89ea7017d3c6186bcda56ea214b8c9fdfeffb9734733a8255aa7e7d0fb87d3df
- Author: prisma
- GitHub username: prisma
- License: MIT
- Repository: https://github.com/prisma/skills/tree/1a9f427e9fe2137298abbcc1a6f372db92e8c40d/prisma-compute
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, env\_access, filesystem, external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/prisma-prisma-compute
- Manifest: https://skillstore.pages.dev/api/skills/prisma-prisma-compute/manifest

## Capabilities

- Evaluates Compute readiness for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, and custom artifacts.
- Creates or updates typed Compute configuration for single applications, monorepos, ports, entrypoints, build output, and environment inputs.
- Selects CLI flows for scaffolding, building, deploying, promoting, rolling back, logging, domains, branches, and project environment variables.
- Diagnoses authentication, workspace, build artifact, branch scope, database, environment, host binding, port, and public ingress failures.
- Explains Compute SDK and Management API patterns for authenticated automation and prebuilt artifact deployment.

## Use Cases

- Prepare Framework Deployment: Check a Hono, NestJS, or Bun application for correct entrypoint, host, port, and environment settings.
- Operate Preview and Production Releases: Select projects, branches, environment roles, deployment targets, verification steps, promotion, and rollback commands.
- Build Platform Automation: Use Compute SDK and Management API guidance to design authenticated deployment tooling with redacted outputs.

## Prompt Templates

### Check Deployment Readiness

```
Assess this Prisma project for Compute readiness. Identify its framework, entrypoint, port, host binding, environment source, and safest next step.
```

### Create Compute Configuration

```
Create or update prisma.compute.ts for this application. Preserve existing behavior, avoid secret values, and explain each deployment default.
```

### Diagnose a Failed Deployment

```
Troubleshoot this failed Prisma Compute deployment. Inspect build output, authentication context, branch scope, logs, host binding, and port configuration.
```

### Design Monorepo Delivery

```
Design a non-interactive deployment workflow for this monorepo. Include target selection, preview isolation, secret handling, verification, promotion, rollback, and failure reporting.
```

## Limitations

- It does not provide credentials, database URLs, workspace access, or deployment authorization.
- It cannot guarantee current CLI behavior without checking installed command help and project files.
- It does not replace framework tests, database migrations, observability, or production change controls.
- SvelteKit requires a custom or prebuilt server artifact because no direct Svelte deployment key exists.

## Best Practices

- Inspect existing scripts, configuration, framework output, and CLI help before changing deployment behavior.
- Confirm workspace, project, branch, environment role, and production intent before any remote mutation.
- Redact tokens, database URLs, environment values, and signed upload links from logs and summaries.

## Anti Patterns

- Do not use placeholder database URLs or commit secret values into Compute configuration.
- Do not deploy production changes with confirmation bypasses unless the user explicitly approves the exact target.
- Do not treat local readiness or build success as proof that public ingress works.

## Security Audit

- Audited at: 2026-07-23T17:35:03.399\+00:00
- Summary: No prompt injection or malicious collection endpoint was found; most static matches are Markdown or deployment documentation. The skill still handles secret-bearing environment files, executes mutable package versions, and documents non-interactive production mutations.

## Stats

- Views: 0
- Downloads: 6
- Favorites: 0
- Popularity score: 0