The product context is becoming part of the design tool.
Cover story · Figma, GitHub and practitioner work · 26–30 Oct
The interesting shift this week is not that more tools can generate a screen. It is that they can now reach further into the work around it.
Figma’s agent can pull Drive research, assets and real data into a file. GitHub’s new Replica asks teams to give prototypes their own components and written rules. In a UX Collective essay, designer Christine Vallaure describes doing the reverse journey: keeping the system in code, then using an agent and MCP to build its Figma library.
That makes context the new design material: useful only when its source, permission, freshness and gaps stay visible. A plausible prototype can still be wrong if it quietly borrows stale research, invents a policy or exposes private data.
For Phoenix: give every agent-assisted exploration a small context envelope: approved components, a safe data sample, the user task, known unknowns and the person who makes the decision.
No current visual post cleared the bar.
Public social scan · 24–30 Oct
We found timely conversations, but no public X post with a verifiable date and useful product-design visual made this issue’s cut. The three showcases above are dated demos and practitioner work, not substitutes passed off as social posts.
A community signal · r/DesignSystems · 26 Oct
One current thread pushed back on generic agent-made systems: useful output still depends on a team’s own patterns and taste. That is an opinion, not adoption evidence—but it is a useful counterweight to polished tool demos.
Read the public discussionWe used public web results and zero-credential discovery only. No authenticated X feed, browser cookies, API keys or paid scraping. The gallery stays short rather than reusing older posts.