Cursor rules for Claude to create working Prisma migrations?

Mar '25 • Full Stack Development with AI

Hey Everyone,

For some reason whenever Claude (within Cursor agent) is trying to update my dev DB it just struggles with the right pattern for generating migrations, updating the schema and generating the client. It seems to be updating things in an incorrect order which leads to Prisma wanting to reset my DB with almost every migration run. This is just in Dev so not a huge deal, but it is annoying when I have it populated with some data to demo and test with. When I was using Cursor to build a Ruby on Rails app it handled all of the Active Record migration creation and running flawlessly.

I'm curious if any of you have some good cursor rules to help it use Prisma correctly?

0 comments