Nurul Sundarani
Nurul is a senior member of the Prisma team working directly with developers to help them succeed in production, with engineering experience spanning payment infrastructure, microservices, and full-stack product work at several companies before Prisma. Nurul's writing draws on daily conversations with teams running Prisma at scale, focused on real problems and practical fixes.
Why Your Agent Reads a Prisma Schema Better Than Your Codebase
Your data model in one declarative file. We measure what a Prisma schema costs an AI coding agent in tokens and type-check time, and what it buys.
Your AI Agent Needs File Storage. Now It Can Get Its Own
Object Store buckets add S3-compatible file storage to every Prisma project. Two Management API calls take an agent from nothing to reading and writing files.
You Don't Need Elasticsearch, Postgres Already Has Full-Text Search
Build full-text search with tsvector, GIN indexes, and pg_trgm typo tolerance on Prisma Postgres. For most apps, no Elasticsearch cluster required.
What to Put in Your AGENTS.md So Your Agent Handles the Database Right
A copy-pasteable AGENTS.md section for database work: ephemeral Postgres via npx create-db, safe migrations, and JSON output for Claude Code, Cursor, and Codex.
You Don't Need a Job Queue, Postgres Already Has SKIP LOCKED
Postgres can run a reliable background job queue with FOR UPDATE SKIP LOCKED. Build a worker queue with retries using pg and Prisma Postgres, no broker required.
Your AI Agent Needs a Database. Give It One in Five Seconds
npx create-db gives coding agents a temporary Postgres database in seconds, no sign-up. JSON output lets Cursor, Claude Code, and Codex test on real Postgres.