Really solid approach to bridging that Figma-code gap. The two-mode system (use vs learn) is clever because most docs either oversimplify or drown people in abstractions. I ran into similar issues when I was working with a design team trying to maintain token consistancy across platforms, and having refernce-quality code made handoff way smoother. Curious how the Figma MCP integration will handle edge cases like nested variants or conditional styles.
Hey thanks so much Neural Foundry! This gives me a lot of validation, I might be in the right direction.
Yes, I am nervous about how Cursor would handle the complex components having nested subcomponents. Not there yet, still kind of brainstorming and learning with ChatGPT and mocking this up with Google AI Studio.
I am thinking I need to maybe work backwards and first create all the smallest components that would be nested and then work on the bigger, more complex components that have these components as children. An interesting challenge.
Really solid approach to bridging that Figma-code gap. The two-mode system (use vs learn) is clever because most docs either oversimplify or drown people in abstractions. I ran into similar issues when I was working with a design team trying to maintain token consistancy across platforms, and having refernce-quality code made handoff way smoother. Curious how the Figma MCP integration will handle edge cases like nested variants or conditional styles.
Hey thanks so much Neural Foundry! This gives me a lot of validation, I might be in the right direction.
Yes, I am nervous about how Cursor would handle the complex components having nested subcomponents. Not there yet, still kind of brainstorming and learning with ChatGPT and mocking this up with Google AI Studio.
I am thinking I need to maybe work backwards and first create all the smallest components that would be nested and then work on the bigger, more complex components that have these components as children. An interesting challenge.
I'll surely write about all of this.