prisma-composer

Write, test, and deploy Prisma Composer apps with typed services and modules.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/Sahil-Showket/ShopSphere --skill prisma-composer-sahil-showket
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-composer
Source: https://github.com/Sahil-Showket/ShopSphere/tree/main/services/auth-service/.cursor/skills/prisma-composer
Command: npx skills add https://github.com/Sahil-Showket/ShopSphere --skill prisma-composer-sahil-showket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a Prisma App with @prisma/composer involves many framework-specific rules — typed service dependencies, RPC contracts, module composition, input schemas, migrations, and deploy stages — and getting any of them wrong fails the build or deploy. This Skill guides an AI through writing, testing, running locally, and deploying such apps correctly. ## Core Features & Use Cases - Service and module authoring: Declare services with compute(), wire typed dependencies, define RPC contracts, and compose reusable Modules with exposed ports. - Data and infrastructure: Add Postgres databases (raw or Prisma-ORM typed), S3-compatible buckets, cron schedules, blob storage, and event streams via first-party modules. - Testing, local runs, and deploys: Test with mockService/bootstrapService, run the whole app locally with prisma-composer dev, tail logs, and deploy or destroy stages with prisma-composer deploy/destroy. - Use Case: Add a scheduled job to an existing Prisma App — define the schedule, expose a trigger contract on the runner service, wire the cron module in module.ts, and deploy to a new stage. ## Quick Start Use the prisma-composer skill to add a Postgres database dependency to my auth service and wire it in the root module.

Frequently Asked Questions about prisma-composer

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

FAQPage Schema
How do I add a Postgres database to a Prisma Composer service?▼

Declare rawPostgres() in the service's deps for a { url } binding you connect yourself, or postgres(contract) for a typed Prisma ORM client. Provision the database in the module and wire it to the service's dependency slot.

How do I test a Prisma Composer service?▼

Use mockService from @prisma/composer/testing for unit tests with typed dependency doubles, or bootstrapService from @prisma/composer-prisma-cloud/testing to boot the real built entry in-process against fake dependencies over HTTP.

How do I run a Prisma Composer app locally?▼

Build first, then run prisma-composer dev module.ts, which starts every service with local Postgres and buckets and no cloud credentials. Use --fresh to wipe local data and prisma-composer log to tail service logs.

Does prisma-composer deploy build my code automatically?▼

No, you must build before deploying. The framework only assembles your built output, so run your bundler (for example bun build or next build with standalone output) before invoking prisma-composer deploy.

Why does my deploy fail with MIGRATION_PATH_NOT_FOUND?▼

The deploy only replays committed migrations and never creates schema itself. After editing contract.prisma, run prisma contract emit and prisma migration plan, commit the migrations directory, then redeploy.

How do I pass secrets and config to a Prisma Composer service?▼

Declare one input schema on the service with secretString() for credentials, bind values at provision() using literals, envParam(), or envSecret(), and read them via service.input(). Secrets are redacted except through .expose().