🚨🇪🇺 BREAKING 🇪🇺🚨
The EU has officially passed the Tailwind Classname Regulation Act (TCRA-359.3).
According to EU bureaucrats, “each additional class emits 0.4g of CO₂” and “classnames like bg-neutral-900/70 backdrop-blur-md are environmentally unsustainable.”
Websites exceeding 30 Tailwind classes must now offset their carbon footprint by planting 1 tree per 10 classes, or face fines of up to €1000 per class.
Hot take: the entire interface around vibe coding is wrong
They all collapse design, flow, and build into one linear chat, which actually makes no sense. They’re code first -> visual last then you fight the code when the idea shifts.
the workflow really should be a visual first loop. explore a bunch of ideas visually -> lock a style system based on favs -> auto scaffold flows/pages -> then compile once
We really should be treating design as the source of truth rather than prompts. “Vibe coding” really should be “vibe designing” and the “coding” should be a button I hit once ive decided on a path.
Once you flip it like that, these linear chat interfaces don’t make any sense, because design is non-linear.
AI is so fast and cheap at generating ideas, so just give me a shitload of ideas, let me narrow it down and expand on it visually, then when it feels right, click build. I don’t want to prompt -> build one idea -> fight to tweak -> repeat. No one does
None of today’s tools hit on this idea end to end, but @Magicpathai and @relume_io are both on the right track i think