The PubHub internal publishing tool at Cisco DevNet underwent a time-constrained redesign in 2026. Instead of following the traditional process of designing first and then implementing, the team had an AI coding agent generate end-to-end interfaces directly from user stories and backend APIs. The result was usable: users could complete the main flows, and the interface connected to the backend. However, designer Alejandro Marrufo and Head of UX Casey Tong wrote in a blog post that "usable" does not equal "finished"—the interface did not follow Cisco's visual language, some AI-generated components were unintuitive, and multiple workflows needed cleanup.
This raised a practical question: how can we leverage AI to accelerate design modifications and integrate them into the final product workflow? Their initial attempt involved converting existing HTML pages back into Figma, allowing designers to continue refining in a familiar tool, and then using a Figma MCP connection to sync changes back to code via the coding agent. The idea was appealing—keeping design work within Figma while AI handled the transfer to implementation.
In practice, three issues emerged. First, details were lost in transit: the round trip between Figma and code missed interactions, complete page and button flows, and animations—the very elements that make an experience feel "finished." Second, updates were slower than expected: modifying the HTML prototype via Figma was slower than the project timeline allowed; some pages even had to be rebuilt in Figma and reconnected to flows before any refinement could begin. Third, the source of truth became blurred: with Figma files and HTML prototypes evolving in parallel, it was difficult for designers and other team members to determine which version was current.
Figma is not without merit. It remains a superior tool for maintaining asset libraries and handling fine-grained UI elements. However, under tight deadlines, it is not the fastest place to refine an interface that is already running in code.
So they tried another path: letting AI coding tools inspect the existing prototype and modify its HTML directly. Design work remained within the existing interface, eliminating reconstruction steps. The HTML prototype became the single source of truth. Designers could make staged changes, review each iteration, and provide feedback to the AI along the way. Design work no longer required rebuilding the interface in a design tool first; instead, it targeted a running implementation directly, including interactions and flows that Figma struggled to capture.
A practical constraint quickly surfaced: token limits. Midway through the project, the designer ran out of tokens, switching from Cursor to Claude, then to Codex, resuming once limits reset. The work survived these switches because the HTML artifact—not any specific tool—held the state of the design. They recommend that teams adopting this approach plan for such constraints in advance.
With this approach, designers could edit and deliver working HTML pages daily, producing new iterations. Under the old Figma-first process, a single page took days. This speed created a compounding effect across the team: faster design output meant faster engineering testing, which in turn meant faster feedback for the next design iteration.