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 & Error Mapping: Covers argument mapping, column type mapping to ColumnTypeEnum, and DriverAdapterError conversion that preserves original database error codes for useful P2039 fallbacks. - 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 to Prisma. Use this Skill to implement the adapter, map driver errors correctly, support nested transactions via savepoints, and validate shadow database behavior for Migrate. ## Quick Start Ask the AI to implement a Prisma driver adapter for your database driver following this guide, including transaction lifecycle, savepoint support, and error mapping.