Persistent Memory & "Do Not Modify" Toggles to Protect Existing Code
As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.
To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.
My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or on/off toggles. This would allow developers to explicitly mark certain functions, files, or UI layouts as "Locked/Remember" (Gemini must preserve them) and others as "Modifiable". This way, we wouldn't have to constantly use defensive prompting to protect the code that is already finished and working.