I’m loving the speed and power of Firebase Studio — it’s honestly amazing how fast you can go from idea to working app. But I’m running into a serious issue with the Prototyper.
Every time it adds new collections, it overwrites my existing firestore.rules with its own default boilerplate. This is particularly problematic for me because I’m using a custom, dynamic security model that doesn’t follow a static structure. When the Prototyper resets the rules, it breaks access to large parts of my app — and I often don’t realize it until something’s already broken in prod or staging.
Is there any way to prevent this automatic overwrite behavior? Or at least a flag to preserve custom rules logic? I’d love to keep using the Prototyper, but right now it’s forcing me to constantly backtrack and restore my rules manually.
When you tell the AI not to do something, sometimes it can be very stubborn. It says yes, I won’t do it and does it anyway. After a few warnings it doesn’t do it a few times and after a few messages it does it again. I think gemini or firebase studio team should do something about this. He keeps adding three inverted quotes at the end of my files too and this causes error. We couldn’t agree on this.
it would be great to have a “explain first” flag, so the prototyper only gives options and strategies instead of starting the implementation right away. at the moment you need to give it that hint with every single prompt. all good until you forget it once…
same. Prototyper deletes unrelated firebase.rules code blocks when it needs to add or remove something else. Also It writes the whole thing again instead of just adding the necassary rule or remove the unnecessary rule. It should not bo rewriting the whole file. Fix would be appreicated.