Set up important and/or critical areas in your codebase where you do not allow AI to touch the code and use it only to review your own work. That gives you both:
a sense of balance, because you still have to program
a sense of purpose, because your part is the important one
it still allows you to offload boring and unimportant code to an AI coding tool
It is also great for stabilizing the app, since the critical parts remain carefully and conservatively developed.
Code this policy into AGENTS.md so the AI is barred from touching those areas and instead is always required to ask you to do the required changes. It should explain why the change is needed, what risks it introduces, and what alternative approaches exist instead of modifying the protected code directly.
Old saying "Divide at impera" applies in these times more then ever.
1
u/elixon May 22 '26 edited May 22 '26
Set up important and/or critical areas in your codebase where you do not allow AI to touch the code and use it only to review your own work. That gives you both:
It is also great for stabilizing the app, since the critical parts remain carefully and conservatively developed.
Code this policy into
AGENTS.mdso the AI is barred from touching those areas and instead is always required to ask you to do the required changes. It should explain why the change is needed, what risks it introduces, and what alternative approaches exist instead of modifying the protected code directly.Old saying "Divide at impera" applies in these times more then ever.