Designers Own Presentation Layer with Claude
UX lead at real estate firm on running a website redesign with Claude Cowork
The real shift here is that design stopped being a static spec and became working front end software before engineering touched it. In this workflow, the designer used Claude to generate HTML, CSS, responsiveness, and animation behavior, then shared a live Vercel link and GitHub repo instead of a Figma file. That removes most of the old back and forth over spacing, motion, and layout, and pushes developers toward data wiring and API integration work.
-
The speedup came from collapsing roles. A project that previously used two designers for weeks, then 10 to 15 developers over roughly three months, was compressed into one designer working about five days, with developers only handling final integrations afterward.
-
This only worked because the output was runnable, not just visual. Claude helped set up Vercel, generated a full HTML and CSS codebase, and let the designer iterate on animations and mobile behavior directly, including using uploaded videos to tune interaction timing.
-
The tradeoff is that AI design handoff creates a new QA burden. The main failure modes were hallucinated copy, missing executive headshots, inconsistent shared components across parallel chats, and loss of context between sessions, which forced careful review and real device testing before handoff.
This points toward a new split in product teams, where designers own far more of the presentation layer and engineering focuses on systems, data, and reliability. As tools get better at preserving context across chats and repositories, more web redesign work will move from mockups to AI generated production ready front ends as the default starting point.