Darren H.

Nope sir. I'm hoping that thorough Rules and instructions will help given the dynamic token and component mapping additions, in theory that feels like it should help it really grasp context in a new way

In my experience so far I'm seeing pretty great speed improvements and accuracy. Yet to dive back into intensive components work which was the weakness so far, not sure 2.1 necessarily addresses that but the newly shipped Rules and Instructions generation may. Just started giving that a go and we shall see

Same model choice. I like what Fable 5 could do but boy it was expensive, 5.1 is brand new and I've not tested it too much but will be in coming days

Much of the same! MCP testing galore, new Claude + Relume + Figma design iteration workflows. Fun stuff Conf - in summary: excited and curious.

Is there any update on the font variables issue above? I believe it's still an active bug

All good. I appreciate the response!

Got you - simple enough workaround by binding these with custom code, but will be nice to get cleaned up! The main issue was not knowing why it was duplicating.. glad to have it figured out!

Matt J. chiming in here with a +1 on this issue. Been driving me crazy trying to figure out why classes are duplicating seemingly at random - I have a clean starter project cloned from the base Relume starter, all that I've done is add variables panel setup and linked up global styles like typography to them, and make a few components. With any component pasted in, heading-style, text-size, and button styles are duplicated just about every time. Read only

Awesome update! With this, when we import to either Figma or Webflow using the respective import tools, are the "edited" wireframes maintained? Or will it pull in the base component?