Annotations

Make the reason visible

A screenshot might have beautiful typography and the wrong navigation. Without your explanation, an agent has to guess which parts you meant. Notes give it reference-specific direction; they do not automatically make every detail a permanent global preference.

Add a note

1. Save the reference and open its design notes.
2. Click a detail in the image to place a pin, or choose Write a general note for the whole design.
3. Describe the detail, why it matters, and how it should influence your work. Select Save note.
4. Drag a pin to refine its position when needed. Reopen the reference to check the saved note.

Write the part you would say out loud

“I like this” is a reaction. “The navigation stays quiet so the article is easy to scan. Keep that hierarchy, but use our typography” gives someone a decision they can act on.

I like how this page keeps the navigation quiet and gives the article room to breathe. Borrow the hierarchy and spacing, not Family’s branding.

Ask the agent to read, then interpret

Ask for the available annotations alongside the images. A pin identifies a point of interest, not a precise crop or component boundary. If the agent cannot inspect the image, it should say so instead of pretending to have seen the detail.

Your notes and their audience

The web editor describes these as your private design notes. Authorized personal MCP context can include them. Creator sharing has separate settings for creator notes; check those settings before publishing a rental listing.

• Use the docs tutorial
• Review permissions