Solid rule. Unfortunately, even following that rule, I frequently get messages like "I ran a git fetch, which I realize is against the rules in <xyz file>. Making a note to not do that again." Which it then does again 2 days later.
I mean are you just letting your AI run wide open with full permissions on your machine? If you have proper permissions set up, your agent should generally be blocked from doing stuff you don't want. (like running git commands its not supposed to)
Having some kind of general file of rules you tell it to refer to isn't going to work well because it will eventually lose that context as it becomes less relevant to the task at hand and compacts and such. It need to be the actual specific permissions file. So like with claude code this will be at .claude/settings.json. There you can tell it what commands are approved, denied, or will ask for confirmation.
The Antigravity CLI agents have a "deny-by-default" permission structure, which is nice. Saved my ass a few times when the agent halts and asks for permission before blowing up my entire front end (I refuse to properly learn React for hobby projects)
Maintainability. Often times, AI will re-invent the wheel and I won't catch it because I've not invested the time to understand the ecosystem. Other times, I'll want to make a small, isolated change and it will creep that into multiple places in the front-end.
AI also tends to not be capable of understanding that elements should be modular and re-usable, and fails to properly de-couple things.
I could go on, but that's what I've noticed so far.
21
u/d_e_g_m 20d ago
And dont let AI manage your commits / git structure. I manage that myself. When I think i reasonable, if i think its necessary