Write a useful design brief
Give your agent the context it needs to make better decisions.
Explain the task
Start with the user and the task. What are they trying to achieve on this screen? What should happen after they take the main action? Include the product context that changes the answer.
“A settings page” leaves many decisions open. “A settings page where team owners can invite members and understand who has access” gives the design a clear purpose.
Include the content and constraints
Share required copy, actions, data and navigation. Mention constraints such as an existing component library, a supported mobile size, accessibility requirements or a brand style that must be preserved.
If you have references, explain what you like about them. A reference can guide the density, hierarchy or interaction without dictating the whole appearance.
Give a usable brief
You can use this structure in your next request:
- Product: what you are building and who it serves.
- Screen: the specific view and the task it supports.
- Content: the information and actions it must include.
- Direction: the tone, references and brand assets to use.
- Constraints: existing components, device sizes and anything that must stay.
- Review: what you want to compare or check before implementation.
Leave room for design
Be specific about requirements and flexible about how they are arranged. Ask for alternatives when the layout or visual direction is still open.
Once you see a proposal, give feedback about the result: what is unclear, what is hard to find, and what feels wrong for the audience. You do not need to prescribe every pixel.
