What problem does it solve? Building a Prisma SQL driver adapter is error-prone: type-compatible code can still corrupt values, leak connections, break transactions, or lose original database error details. This Skill provides the exact contract, priority rules, and verification checklist needed to implement adapters that behave correctly with Prisma Client and Migrate. ## Core Features & Use Cases - Adapter Contract Implementation: Guides implementation of SqlDriverAdapterFactory, SqlDriverAdapter, Transaction, and migration-aware shadow database factories against the installed @prisma/driver-adapter-utils version. - Transaction & Savepoint Protocol: Enforces one dedicated connection per transaction, lifecycle-only commit/rollback hooks, and connection-local savepoint handling for nested transactions. - Result & Error Mapping: Covers argument/column type mapping, 64-bit integer precision, and DriverAdapterError conversion that preserves originalCode and originalMessage for useful P2039 errors. - Use Case: You are writing a new database driver adapter for Prisma 7 and hitting P2039 errors or transaction leaks; use this Skill to audit your transaction lifecycle, savepoint hooks, and error mapping against the official protocol. ## Quick Start Ask the AI to review or implement a Prisma driver adapter's transaction and error-mapping code using this Skill's contract and verification checklist.