Taste Previews

Try a direction before committing to it

Taste Previews provides a review surface for generated UI directions. Use it when you want to compare possibilities or refine a particular version before applying changes to your app. Availability depends on the connected server, account, and client; not every MCP client can generate or embed a preview.

Start from the actual project

Connect Taste and ask your agent whether Preview tools are available. Have it inspect your current page and project context, including the design system and the collection you want to use. Explain what should change and what should stay.

A useful starting point has evidence of the current design, not just a guess about it. If the agent cannot capture or inspect that evidence, have it explain the limitation before generating.

Give the exploration a boundary

Review and refine a specific version

Open the preview the agent returns. Inspect the rendered interface and its context or limitations. Compare it with the current page: did the requested change happen, and did the details you wanted to preserve survive?

When asking for a revision, identify the version you mean. Use the available history to revisit earlier work and continue from that version, rather than describing a direction ambiguously. A request being sent does not by itself mean generation finished.

Carry forward decisions deliberately

Tell the agent which decisions you accept and which you reject. Where project memory is available, ask it to save only the confirmed rules for the correct project. Exploration history should not silently become a global preference.

Ask the agent to implement the selected direction in the real codebase, then test actual interactions, responsive behavior, and accessibility. A convincing preview is not proof of a working production implementation.

• Use an existing design system

Know when it helped