Ask HN: Would developers use a Figma-style editor for Tailwind CSS?

[abhaysinghr516]

I'm considering building a visual editor for Tailwind CSS that combines:

- Visual manipulation (draggable handles for padding/margin) - Direct class editing on element click - AI-assisted styling through prompts - Component-based drag and drop system

The goal is to make Tailwind development more visual while maintaining code quality.

Questions for the HN community: - What's broken about current Tailwind workflows? - Would visual editing help or hinder development? - How would you use AI in this context?

Looking for critical feedback before starting development.

[fpereiro]

This could be interesting. My team works with Tailwind and we don't have a workflow that brings anything from Figma into Tailwind. So basically, we put Figma and our Tailwind prototype side by side, and make the latter converge to the former by trial and error.

[abhaysinghr516]

Thanks for sharing! Exactly - I want to bridge that gap between Figma and code by combining v0.dev-style AI generation with Figma's visual editing capabilities. The idea is to eliminate that back-and-forth by letting you visually edit while the code updates in real-time, plus use AI prompts to speed up styling. I would love to hear if your team would find that workflow helpful!

[brudgers]

Build it and find out because:

+ what people will say when imagining a tool is different from what the will do when considering an actual tool.

+ research is safer than building.

+ research is easier than building.

+ no amount of research is building.

+ research is trying to solve problems you don't have.

It's ok to have an idea and not want to do the hard work to make it happen and hard work without driving enthusiasm is often not worth doing.

Good luck.