Private beta
/fuː/ like foo, or /foʊ/ like foe. We aren’t particular.
Design-dev handoff for the agentic age.
Redesign in the live product, and when it looks perfect, ship that.
Three ways in
Select an element and change its CSS in DevTools the way you already do. Foux tracks every edit against the baseline it took when you started. Nothing generated, no model involved. The quickest way to answer "does this look right?" on the real page.
Paste a frame URL and Foux takes colors, type, and spacing from the file itself rather than from a picture of it. Landing those values in your real styles is what shows up the difference between how a design looks in Figma and how it looks on the page. Code Connect could take this further, into your design system.
When the design isn't in Figma — an export from any tool, a comp, a photo of a whiteboard — Foux works from the picture. Values are read off the image, so the run lands on intent more exactly than on numbers. We'll see how far this one goes as model vision improves.
Why it works this way
Design already decides how the product should look. Foux carries that as far as the real page, so the answer comes from the person with the taste for it.
Prompting a front end has never been easier, and it shows. Generate enough of it and products drift toward the same handful of shapes. This is how we end up with everything the same blue-purple gradient.
A change that travels as a picture and a paragraph gets read honestly, reasonably, and differently. By the time the difference surfaces in review, saying "not quite" costs a second ticket, so it often goes unsaid.
Which element, what it should become, and whether the result on the real page is actually right — decided before anyone is asked to build it, and revised without asking again.
For the developer
Foux reads the live element and the design, rebuilds it in place, and opens a draft pull request written in the style of your codebase. But it stops at the edge of the component. It doesn’t put new hooks into your state or wires to your APIs. That is left for you, or your agent, with clear markers to where the wiring goes.
No SDK, no dependency, no build step. Foux reads the live page from the browser. Close the pull request and there is no trace it was ever there.
New components land in their own directory. The only existing file it edits is the parent that renders them. That boundary is enforced in the pipeline, not left to good behavior: a run that reaches past it fails instead of opening a pull request.
Foux is going out to a small first group of designers and front-end teams. Tell me what you’d point it at and I’ll be in touch.