Cursor was huge but it only solved half the problem

We also need a code-aware browser that lets you point and click UI elements and trace that element back to the piece of code that generates it

vibe coding rn is [ide → app]
it should be [ide ←→ app]

✨ Be the training data you want to see in the world ✨ | DΞF | Head of Product Serotonin | building serotonin.co/platform

how different is it from inspect element on browsers?

currently @openrank prev: buidl.so, threads_reader
https://dharmi.notion.site

There are some browser extensions that make it easier but with all the virtual dom shenanigans that happen in things like react it can be hard to trace ui back to the original component

Ideal state I just point at something on the browser, say "move this 2px up" or "display this to Fahrenheit" or "add thing xyz to this dropdown" and the browser feeds that request back to the ide with the correct component as context

Ohh, a browser that doubles down as a figma canvas with dev mode directly feeding details back to cursor/IDE will be 🔥