AI can make a screen. Your team decides what belongs.
Surfaces makes the design rationale visible before a generated screen moves into handoff.
Looks right is the dangerous part.
A generated screen can match the visual system and still leave the design rationale unclear before handoff.
A reviewer has to infer which source, state, and next step shaped the UI.
The open question, owner, evidence, and next step stay close to the screen.
Before review
Designers explain what the screenshot missed after the work has already spread.
With Surfaces
The design rationale stays beside the screen while the team can still change it.
The few questions that change the outcome.
Surfaces keeps the conversation close to the generated work, where designers, engineers, and leaders can all read it.
Source
Which pattern, term, or brand choice belongs here?
Behavior
What must stay true for accessibility, loading, errors, and state?
Owner
Who can resolve the open question before the work is treated as ready?
Review context
The source, rationale, owner, and next step stay close to the generated screen.
Handoff gate
Open questions stay visible before work moves into design review, engineering, or sharing.
Shared memory
The decision stays attached long enough for the next person to understand the work.
One screen, fewer hidden assumptions.
The moment is simple: a screen that looks ready still needs the review context beside it.
Designers stay in control.
The source and behavior are visible before review turns into cleanup.
Engineers inherit less ambiguity.
The reason travels with the screen instead of arriving as a guess.
Leaders see where risk remains.
The team can tell what is ready to share and what still needs a decision.
Make the next generated screen easier to review.
Keep the rationale, owner, and next step visible before it moves into handoff.