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 for implementing adapters against @prisma/driver-adapter-utils in Prisma ORM 7. ## Core Features & Use Cases - Contract Implementation: Guides implementation of SqlDriverAdapterFactory, SqlDriverAdapter, Transaction, and optional savepoint hooks with correct connection lifecycle. - Result and Error Mapping: Covers argument mapping, column type metadata, DriverAdapterError conversion, and preserving originalCode/originalMessage for useful P2039 errors. - Transaction Safety: Enforces one dedicated connection per transaction, lifecycle-only commit/rollback hooks, and connection-local savepoint handling. - Use Case: You are adding a new database driver adapter for Prisma 7 and need nested transactions, shadow database support for Migrate, and correct error mapping without leaking pooled connections. ## Quick Start Ask the AI to implement a Prisma 7 SQL driver adapter for your database driver following the transaction, savepoint, and error-mapping rules in this Skill.