Web designers used to be the combination of what you'd today call UX designers and frontend developers. The technical knowledge and understanding in the UX-only tribe that seems to have become the majority is abysimal. They are nearer to product management than to engineering. The capability of their current tools enables to cheaply spit out high-fidelity prototype which are good enough to give the technically clueless business completely false impressions about the cost for the promised capabilities, ever increasing the demand and sophistication of the actual engineering part of the frontend.

I don't see that being automated by language models in the sense of that it would enable the technically unsophisticated designers of today to come up with even an actually deployable UI, let alone one that is maintainable, so that a change in requierements would not lead back to square one.

I'm willing to be a spectator in attempts of business to chase that folly, though. Once systems start to degrade engineering demand will go up.

I'm already seeing it. Our BE team is now expected to churn out FE applications.

BE will generate FE templates and to wire it up to the API they built

FE, designers are screwed. BE is safe.