Your Taste Profile
A broader picture of what you tend to like—and what you do not.
How Taste learns from you
Your saved references, uploaded samples, portfolio signals, and design reactions can contribute to profile generation. The profile turns those available signals into written design direction. It is an interpretation to inspect, not an instruction that overrides the project you are building.
Give it honest preference signals
On Rate, swipe right for I love it, up for It’s OK, or left for Not for me. You can also use the labeled buttons. It’s OK is a real reaction, not a skip. A mix of honest positive and negative reactions is more informative than approving everything.
Generate and review
Open Taste Profile to check readiness and generate or regenerate the profile. The current readiness rule is at least five reference signals, or at least twenty reactions including three positive and three negative reactions. The page shows eligibility and the next available refresh time.
Read the resulting description. If it misses your intent, add more representative references and clearer signals, then regenerate when available. Do not assume a single new save instantly rewrites the profile.
Live access does not mean instant synthesis
MCP reads the stored profile when requested. Adding a reference, regenerating the profile, and asking the agent to read it again are separate steps. A local skill export is a snapshot and can lag behind your account.
Apply preferences in context
Read my current Taste Profile and the project’s design system. Tell me which preferences can improve this screen within its existing components and accessibility requirements. Identify any conflicts before changing the design.
What success looks like
The profile sounds like your preferences, and the agent can distinguish those preferences from this project’s constraints.