Your first project
Start with one screen, a few useful references, and a clear reason for each.
Choose something specific
“Make my app look better” leaves a lot to guess. “Make the settings screen easier to scan while keeping our existing components” gives the work a purpose. Pick one surface before collecting references.
Collect with a question in mind
- Open Discover and save a few designs that solve a similar problem.
- Open Saves and create a collection named for the work, such as Settings or Onboarding. Add the saved references to it.
- Upload a screenshot of your current screen as inspiration if you want it alongside the references. Keep work you cannot share out of public uploads.
- Open each reference and write a note about the particular detail that matters.
Bring the collection into your project
Connect Taste to your coding tool, complete sign-in, and verify it can list your collections. Then ask it to inspect the references before making changes.
Find my “Settings” collection in Taste. Inspect its reference images and my notes. First inspect this project’s existing components and design tokens. Propose three specific improvements to the settings screen, then implement them. Tell me what context you could not access.
Review the result, not just the resemblance
Check the screen with real content, narrow widths, keyboard navigation, and long labels. Ask which reference influenced each decision. Keep the changes that make your product work better; revise the notes when the direction changes.
What success looks like
The agent can name the collection, describe a note you actually wrote, and explain how it applied that note to your screen.