The tool sequence designers actually used, by discipline. See how the stack shifts as AI takes more of the execution.
Designer writes the brief and the constraints. Agent generates flows, components, and working code in one pass. Designer reviews, rejects, redirects.
57 synthesized monthsin the data layer. Stage breakdowns (Starter / Scaler / Titan) are available for 2026 only — earlier months show under the All segment but won’t appear under stage filters until the design-context pipeline runs further back.
Product designers direct agents per feature. They write intent docs, set guardrails from the design system, edit output, ship to code agents. The unit of work is a decision, not a screen.
Designer writes intent, agent ships a working prototype against the design system, designer edits in canvas and code interchangeably. Specs are dead. The artifact is the running thing.
Prompt-to-prototype is default. Designers ship working flows, not flat screens. Design engineers turn those into production.
Prompt-to-prototype is the default first draft. Designers edit and direct rather than build from scratch. The Figma file is increasingly a review surface, not a construction surface.
Designer writes a brief and a system reference. Agent generates flows and code. Designer reviews, rejects, edits. Ships behind a flag.
Product designers started flows with Google Stitch or v0 — generating five-screen canvases from a single prompt to pressure-test navigation logic before touching Figma. From there, they refined interaction details inside Figma, used AI plugins to generate copy and component variants, then pushed to Maze or Lyssna for rapid usability validation. The blank-canvas starting point is effectively dead; the job is now editing and directing generated flows rather than drawing them.