A novel recommendation to mitigate frustrating agent/assistant encounters

[pr99az]

you should have a file in your repo as per these forum posts:

A .rules File to Keep the Replit Agent from Going Rogue

I’ve had to basically give up on replit, abuse or now just as the hosting, and have moved to cursor. The main reason is replit will just destroy your database and data. It cannot be told to STAY AWAY for making database changes and to ask for confirmation before making big changes. Until it has a way of staying in it’s lane, and ideally also forcing agent to confirm a plan with you it’s pretty useless unless you’re just building something throw away and just for a demo.

Devguidelines.md a file everyone needs

It’s also super helpful to ask Claude or ChatGPT to create a Product Requirement Document ( PRD ) Ask it to break it down into phases and suggest using the Replit Agent or Replit Assistant and it does a pretty nice job of breaking it down.

add a rule instructing the agent to read your codebase first. you can also select files to help it understand which areas to consider as priority.