What problem does it solve?
Prisma v7 driver adapters are hard to implement safely because they require exact contract behavior for transactions, error mapping, and SQL/result typing that is not reliably inferable from examples.
Core Features & Use Cases
- Adapter contract & architecture: Defines the PrismaClient → SqlMigrationAwareDriverAdapterFactory → SqlDriverAdapter → Transaction responsibilities and how Prisma routes SQL calls.
- Deterministic interface coverage: Specifies the required types and methods (queryRaw, executeRaw, executeScript, startTransaction, dispose, plus Transaction commit/rollback semantics).
- Correct transaction lifecycle: Ensures commit() and rollback() act as lifecycle hooks only (no SQL), while Prisma sends COMMIT/ROLLBACK through executeRaw.
- Robust mapping requirements: Covers argument mapping, row mapping, column type inference, isolation level validation, and database-specific error mapping via DriverAdapterError/MappedError.
- Practical implementation checklist: Provides a verification list to confirm the adapter meets Prisma’s expectations before being considered complete.
Quick Start
Use the prisma-driver-adapter-implementation skill when implementing or modifying a Prisma v7 SqlDriverAdapter or Transaction so you follow the required transaction lifecycle, argument/row/column type mappings, and error mapping checklist for your target provider.