Furqan

You can author Prisma 8 contracts and migrations, write db.orm/db.sql/db.query queries, deploy apps on Prisma Platform with branches and preview environments, manage Prisma Postgres and storage buckets, and compose and test services using @prisma/composer modules and mock services.

They target full-stack and backend engineers building applications on Prisma 8 (@prisma/orm-postgres, @prisma/orm-sqlite, @prisma/orm-mongo), teams hosting on Prisma Platform, and developers composing services with @prisma/composer. They explicitly exclude Prisma ORM 7 or earlier using schema.prisma and @prisma/client.

Invoke them when editing contract.prisma or contract.ts builders, running prisma contract emit, prisma deploy, prisma dev, or prisma auth, configuring prisma.config.ts with definePrismaConfig, or wiring composer services via compute(), module(), and service.load() in local or deployed environments.

You need a project depending on Prisma 8 release candidates (@prisma/orm-postgres 8.0.0-rc.11 or platform library 8.0.0-rc.15) or @prisma/composer 0.20.0. Recognized signals include @prisma/orm-* imports, contract.json/contract.d.ts files, and the prisma-composer CLI.

No. The Prisma 8 skill explicitly excludes Prisma ORM 7 and earlier, which rely on schema.prisma and @prisma/client. Coverage is limited to Prisma 8 contracts, Prisma Platform operations, and Prisma Composer service composition, including Supabase extension and RLS integration.