I think React is one of those areas where consistency is more important than individual decisions. With a lot of front-end webdev there's many right answers, but they're only right if they are aligned with the other design decisions. If you've ever had to edit a web page with three different approaches to laying out the CSS you know what I mean.

LLMs _can_ do consistency, they're pretty good continuing a pattern...if they can see it. Which can be hard if it's scattered around the codebase.

> one of those areas where consistency is more important than individual decisions

This describes any codebase in any programming language

This is why "programming patterns" exist as a concept

The fact that LLMs are bad at this is a pretty big mark against them

Consistency is why frameworks and libraries exists. Once you start to see consistency in your UI views, that's a good sign to further refine it into components and eliminate boilerplate.

> LLMs _can_ do consistency

They won't even consistently provide the same answer to the same input. Occasional consistency is inconsistency.

My favorite is when I ask it to fix a bug, and in the part of the code that doesn't change it still slightly rewords a comment.