Agree the look
before the first screen.

Color directions, light and dark together: Group each candidate direction with its dark counterpart and name it. Deciding both at once avoids the very common outcome where dark mode is a separate product with a separate personality.

Type at real interface sizes: Set the actual labels, body, and numerals at the sizes they will ship at. A typeface chosen from a specimen at 96px regularly falls apart at 13px, and that is where interfaces actually live.

Density and spacing character: Pin a dense reference and a generous one side by side and decide which product this is. Density is a positioning choice, not a spacing token, and teams that never decide it end up negotiating it screen by screen.

Motion and interaction references: Capture screen recordings and frames from real apps so the motion register is agreed too. Motion is the layer most likely to be invented ad hoc by whoever builds the component first.

Prompt against the whole canvas: Ask it to add an empty-states and error-states section, lay out a second colder color direction, or build a competitor row for an adjacent category. It reads what you have built.

It structures, it does not decide taste: Storyflow lays out and organizes the direction. Which reference is right for this product stays with the designer, because that judgment is what you are being paid for.

Iterate without losing work: Re-prompt as often as you want. Screenshots you have already placed and grouped stay exactly where they are while the AI builds around them.

Brand assets on the same canvas: Pin the logo, brand palette, and marketing site beside the interface direction. Products drift from their own brand constantly, and the drift is invisible until both are on one surface.

The intent statement in the built-in editor: Write a paragraph saying what the product should feel like and why, next to the references that justify it. Statements written alone drift into ambition; statements written beside evidence stay usable.

Two directions, side by side: When there are two credible looks, build both and put them next to each other at the same scale. Stakeholders choose far better between visible options than between one option and a description.

View-only links, no account required: Send the board to a founder, an engineer, or a client and they open it in a browser. No Figma seat, no signup, no exported PDF that goes stale the moment you change your mind.

Comments on the reference itself: Feedback attaches to the screenshot or swatch it concerns. This is what turns it feels a bit corporate into a note about the specific reference that caused the reaction.

Hand off to the design file: When the direction is agreed, export it and take the decisions into Figma to build components and screens. The board stays as the record of why the system looks the way it does.