Lee Sun-woo

Give every reference a role

A current screen, a reference image and an abandoned mockup can all be useful inputs to an AI. They become confusing when they arrive without an explanation of which one governs the change.

For interface work, I treat the design brief as a way to assign those roles. The model needs to know what exists, what is open to change and what a reference is meant to demonstrate.

Resolve the conflict before requesting a design

Consider an illustrative search-screen task. The current product has a sidebar. An old mockup has a bottom tab bar. A reference has an attractive relationship between the query and result count. Asking the AI to “use these and stay consistent” leaves it to decide which navigation is current and how much of the reference to copy.

A compact brief can settle the ambiguity:

Illustrative brief: The implemented search screen defines the current navigation and controls. Keep those. Use the reference only to explore how the query and result count are grouped. The mockup with bottom tabs is historical. Review the result with a long query and an item missing its description.

This gives each input a different job. The current product supplies constraints, the reference supplies an idea, and the content examples test the result. The historical mockup can explain a past decision without becoming a second specification.

Illustrative brief. Keep the current constraints, borrow from the reference, and leave the old mockup behind.

If the code and the supposedly current screen disagree, the brief has not yet resolved the starting point. That conflict deserves a specific question before a broad edit. Adding another reference will not settle it.

Curate the next decision’s context

Anthropic describes context engineering as curating and maintaining the information available to a model during inference. The term covers more than prompt wording: tool results, documents and conversation history also influence the next action.

For design, my practical application is to preserve the accepted decision and its reason. After choosing the query-and-count grouping, keep that choice, its constraints and a representative example available for the next edit. A transcript of every discarded arrangement can make an obsolete idea appear current again.

This is not an argument for the shortest possible brief. A difficult interaction may need detailed state descriptions. The test is whether each piece of context helps resolve the decision at hand, and whether a collaborator could tell which source to follow when two disagree.