figma.com
Design analysis
A transition section explains that design context, codebase, and agents remain connected, with a large open visual/demo area and a small exploration link.
Prompt preview
## Reference images Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language. - Component: https://kage-design-assets.t3.tigrisfiles.io/components/figma-agent/07db1d51-fc5a-42e3-8555-5aed12aa6731-1791439427-6.webp - Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/figma-agent/07db1d51-fc5a-42e3-8555-5aed12aa6731-1791439335233-full.webp - Component on Kage: https://kage.design/component/figma-agent-feature-grid-4 ## Before you start Ask what the user's product, audience, and brand are, then apply the principles below to that product rather than reproducing the reference. Design a workflow feature section that explains how the product keeps context connected across stages. Place a concise heading and muted supporting copy in a readable centered or offset column, then reserve a large visual region for a workflow diagram, product demo, or interactive preview. Add a small text link near the visual edge for deeper exploration and an optional circular play affordance. Use generous vertical spacing, a white background, black heading text, gray copy, and a restrained visual system so the relationship between stages is easy to understand. The section should support progressive disclosure: overview first, details on interaction. Never: - use logos, product names, copy, illustrations, or imagery from the reference - reproduce the exact workflow diagram or demo imagery - hide the key relationship behind animation only
kage