Prisma SQL Driver Adapter Implementation
Reference for implementing Prisma ORM 7 SQL driver adapters — contract, transactions, savepoints, error mapping
- What
- Reference for implementing Prisma ORM 7 SQL driver adapters — contract, transactions, savepoints, error mapping
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Prisma team's required reference for anyone implementing or modifying a SQL driver adapter: it lays out the full contract (`SqlDriverAdapterFactory`, `SqlMigrationAwareDriverAdapterFactory`, `SqlDriverAdapter`, `Transaction`) with the priority rules that keep adapters safe — one dedicated connection per transaction (never shared adapter-global depth), `commit`/`rollback` as lifecycle cleanup hooks rather than a second SQL commit, savepoints living on the `Transaction` object (optional, only where the provider supports them), and original database error code/message preservation so unmapped failures surface as useful `P2039` errors. It goes deep on value mapping (arg types respected, 64-bit integers without JS truncation, decimal to `Numeric`, binary to `Bytes`, dates to their explicit types, unsupported natives to `DriverAdapterError`), provider-aware `executeScript` (never naive `;` splitting — it breaks functions, triggers, and quoted strings), factory ownership and `dispose()` semantics, isolated shadow databases for migrations (never pointed at the primary), and a verification checklist from typecheck against the exact `@prisma/driver-adapter-utils` version to concurrent-transaction and dispose-ownership tests. By @prisma, listed here with credit to its creator. Honest caveats: this is protocol-boundary engineering — type-compatible code can still corrupt values, leak connections, or break transactions, and this guide is for adapter authors, not application developers; always work against the exact `@prisma/driver-adapter-utils` version installed by the target Prisma release. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Prisma SQL Driver Adapter Implementation" for me. Reference for implementing Prisma ORM 7 SQL driver adapters — contract, transactions, savepoints, error mapping Repository: https://github.com/prisma/skills/blob/main/prisma-driver-adapter-implementation/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "prisma-driver-adapter-implementation". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.