In your tool an anti pattern that I found was that it seems to use inline styles and css class names of sort 'font-normal' 'text-gray1', etc. That's unmaintainable for large code base.
On the other hand having `copy CSS attributes` contextual menu item in Sketch is super productive. I can choose my own class name and whatsoever and still have the exact styles as the designer wanted them to be.
Actually lots of companies use micro classes. I first learned about it using Tachyons and built a full compliance platform. It’s good because you don’t need to worry about unintended visual changes and bad because you can’t make large style changes without lots of effort.
`text-gray1` means what? Which library am I supposed to use in order to make this stylesheets work? Does it match tachyons or tailwind - no. So I have to add X lines of CSS to my project coming from a tool that I am not able to use once I change a simple class name? Not a good start.
The software also can generate BEM like you wish for in the future. One of our earlier iterations did do that, but the default stack today is Tailwind which I've found to be the second best way to approach CSS (the first is CSS-in-JS, but with explicit design scales).
BTW I took a look at your CodeGen project, and I'm impressed.
Here's a short demo: https://youtu.be/Yi0BjSM3v4w
It eliminates weeks and months of tedious design to code conversion and you can build sophisticated SaaS applications, content-rich pages, and e-commerce portals much faster.
It might help designers who're interested in understanding how their design translates into code because they can instantly see the underlying code for each design, play around with it, and see how it changes.