prisma-platform-core-concepts

Explains Prisma Platform concepts for deploying services, databases, and preview environments.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Furqan-7/bms-app --skill prisma-platform-core-concepts-furqan-7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-platform-core-concepts
Source: https://github.com/Furqan-7/bms-app/tree/main/packages/prisma/.cursor/skills/prisma-platform-core-concepts
Command: npx skills add https://github.com/Furqan-7/bms-app --skill prisma-platform-core-concepts-furqan-7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying and operating apps on the Prisma Platform involves concepts that change quickly and are easy to get wrong: branches as preview environments, service versions, environment-variable classes, and secrets shown only once. This Skill gives an AI agent the authoritative, version-matched mental model of the platform so it deploys, promotes, and troubleshoots correctly instead of relying on outdated training data. ## Core Features & Use Cases - Resource model guidance: Explains workspaces, projects, branches, services, versions, Prisma Postgres databases, and S3-compatible buckets, and how the Composer module declaration drives convergence on deploy. - Deployment workflows: Covers GitHub-integration deploys, CLI deploys with prisma deploy --stage, promotion, zero-downtime rollback, custom domains, and the local prisma dev stack. - Failure-mode reference: Maps ten common failures (lost secrets, reclaimed previews, sleeping services killing background work, missing Temporal global, invalid stage names) to their fixes. - Use Case: You push a feature branch and need a preview environment with its own database. The Skill explains that the branch is the environment, that it gets a fresh empty database wired as DATABASE_URL, and that deleting the git branch tears everything down. ## Quick Start Ask the agent to deploy your Composer module to a preview stage and explain how its database and environment variables are resolved.

Frequently Asked Questions about prisma-platform-core-concepts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a preview environment on the Prisma Platform?

Push a git branch with the GitHub integration connected, or run prisma deploy module.ts --stage <name> from the CLI. The branch itself is the preview environment; there is no separate preview object to create, and the stage name must be a valid git ref name.

How do Prisma Platform preview branches get databases?

A preview branch that declares a database gets a fresh, empty Prisma Postgres database wired in as a branch-scoped DATABASE_URL. Schema comes from committed migrations; production data never carries over unless you explicitly point to it.

Why did my Prisma Platform preview environment disappear?

Preview environments are torn down when their upstream git branch is deleted, and idle unpinned previews can be reclaimed automatically. Push or deploy the branch again to re-create it; the new database starts empty.

Why does background work stop running in a deployed Prisma service?

Idle services sleep: the platform snapshots memory and resumes on the next request, interrupting setTimeout, setInterval, and floating promises. Wrap background work in waitUntil or a KeepAwakeGuard from @prisma/compute to keep the instance awake.

Can I read back environment variable values from the Prisma Platform?

No. Environment variable values are write-only by design: listing shows names and scopes, never values, and no API returns them. To change a value you replace it, then re-deploy or promote since variables resolve at deploy time.

Why does my deployed service throw on the first timestamp read?

The Compute runtime has no global Temporal, so reading an ORM DateTime column throws RUNTIME.TEMPORAL_UNAVAILABLE. Add the temporal-polyfill dependency and import 'temporal-polyfill/full/global' at the service entry, or use the *String column types.