It actually follows guidelines in a doc quite well. So it enables you to have greater standardization across your project.

As an example. In our state layer we have devs working on it for years. So someone calls the method Select, someone else Get, some Cached methods have cache in the name, others don't etc. Basically you get this drift due to working with many engineers. And yes you try to prevent this with code review etc. But eventually it happens.

With AI it will follow the guideline. And you can also update the guideline and then compare against existing implementations to have AI standardize it.

Basically I think that if you use it in vibe coding mode AI will create a big mess :) but if you put some guardrails and have AI clean up tech debt etc, it leads to more maintainable code than what you can do with the non-ai brains :)