Explore
MCP servers and skills: search, filter by where they run, and compare.
MCP servers and skills: search, filter by where they run, and compare.
Skills under test: prisma next migration review , prisma next migrations .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next migration review .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.9 release, migration.json no longer carries fromContract or toContract . The schema rejects those keys as unknown, so any committed manifest that still inlines them fails to load wit
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next debug , prisma next migrations .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next migrations .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.10 release, the SQL family's contract serializer ( familyInstance.validateContract , the seam every on disk contract read now crosses) is strict about the storage.types polymorphic s
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next contract , prisma next migrations , prisma next feedback .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next contract , prisma next migrations , prisma next queries , prisma next build , prisma next debug , prisma next feedback .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next contract , prisma next migrations , prisma next queries .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next quickstart , prisma next contract , prisma next migrations , prisma next queries .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.17 release, every content hash Prisma Next mints or accepts is bare lowercase hex — the sha256: prefix is removed across the board: emitted contract.json / contract.d.ts (including t
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.17 release, every content hash the framework mints or accepts is bare lowercase hex — the sha256: prefix is removed across the board: emitted contract.json / contract.d.ts (including
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.10 release, the SQL family's contract serializer ( familyInstance.validateContract , the seam every on disk contract read now crosses) is strict about the storage.types polymorphic s
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.9 release, migration.json no longer carries fromContract or toContract . The schema rejects those keys as unknown, so any committed manifest that still inlines them fails to load wit
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! TML 2843: @prisma next/sqlite gained a facade level transaction API ( SqliteClient.transaction() + SqliteTransactionContext ), mirroring the existing Postgres facade. Purely additive public surface
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Contributor guide for the Prisma Next skills cluster. If you are using the skills, read [ README.md ](./README.md) and stop here. If you are authoring or maintaining a skill in this cluster, read this
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Who stands behind it