Has anyone figured out a good way for helping the LLM using the MCP server to bridge the gap between the visual info (say, the color of a Button in the design) and the relevant component's properties (say, the correct `variant` that yields that color button)?

We don't have Code Connect hooked up yet, but I'm skeptical that this would solve this particular disconnect because our components all use design tokens under the covers and all we see in the code are different properties that drive those behaviors. The LLM can’t see that using “emphasis” as a `variant` value will yield a blue button, for example.

Interrogating the LLM on what it knows about the selected component yields a bunch of styling details, css, etc. so it knows what color the button should be, in my example, and I've given it our component docs so it knows what the valid variants are, but it can't bridge the gap between the two because there aren't enough dots to connect.

This WOULD be solved via the "Component info" panel, where the appropriate `variant` value is set because the component was added from our library’s Figma design file, but this info doesn't get sent via the server which feels like a huge missed opportunity. Just wondering if folks have figured out clever workarounds for this kind of thing.