What problem does it solve? Multi-tenant applications risk data leaks when queries forget to filter by tenant, and serverless deployments on Neon PostgreSQL require different connection strategies than long-running workers. This Skill enforces tenant isolation at the Prisma client level and standardizes migrations, IDs, and connection configuration. ## Core Features & Use Cases - Automatic Tenant Isolation: A Prisma client extension injects tenantId into every find, create, update, and delete operation so queries can never cross tenant boundaries. - Neon Connection Management: Separate pooled and direct connection URLs for Vercel serverless functions, Fly.io workers, and migrations. - Migration & Branch Workflows: Standard commands for creating and deploying migrations, plus Neon branch workflows for testing schema changes per feature. - Use Case: When adding a new Order model to a SaaS app, use this Skill to define the schema with cuid2 IDs and tenantId, run prisma migrate dev against a Neon branch, and query it safely through getTenantPrisma(). ## Quick Start Ask the AI to add a new Prisma model with tenant isolation and generate the migration for the Neon database.