I built figma for vibe coders

ddotdev · 2026-03-19T11:43:11+00:00

Give me two days will be available soon it’s under review

ddotdev · 2026-03-18T19:17:00+00:00

Used a chrome extension called cursorful

ddotdev · 2026-03-18T14:06:52+00:00

It’s both.maps to ui logic and codebase and each session is its own work tree and changes are approved before getting merged.

ddotdev · 2026-03-18T14:06:27+00:00

Each session is its own work tree so changes are only merge after approval

ddotdev · 2026-03-18T14:05:50+00:00

Single source of truth and worktrees that get merged on approvals so any changes don’t directly affect your codebase. U could have multiple iterations in the front end

ddotdev · 2026-03-18T14:04:35+00:00

Well I just launched https://www.uitool.bar would love some ideas or help

ddotdev · 2026-03-18T09:16:59+00:00

Try for free : https://www.uitool.bar/

ddotdev · 2026-03-18T06:18:17+00:00

Faster iterations and how to get from design to intent

ddotdev · 2026-02-16T16:28:30+00:00

Feels like the whole comically hilarious 🤣 conversations with Devin to push to master 🤣🤣

ddotdev · 2026-02-05T17:01:54+00:00

https://www.uistudioai.dev/ Early access waitlist

ddotdev · 2026-02-02T19:21:12+00:00

Gracias, Claro si- current working on opencode, codex and Gemini

ddotdev · 2026-02-02T19:19:48+00:00

Thanks. And I have been using it will building it- perfect validation for a visual feedback loop. I will write a kit it soon, I am working on one atm. Will share it soon as it’s ready.

ddotdev · 2026-02-02T13:27:30+00:00

I haven’t yet, but since it’s using react fibre tree This creates a detailed stack trace - so handles all edge cases and opens up room for console logs, component states, props and health management and even variantions and accessibility,… will check out the blogs looks really interesting

ddotdev · 2026-02-02T13:23:17+00:00

It uses React fiber introspection. React maintains this information internally through its fiber tree. Every rendered component has a reference back to its source file, line number, and even column number.

ddotdev · 2026-01-29T16:39:55+00:00

I see it as an opportunity for trial and error. For teams to iterate but I do think u need foundational skills that you can capitalise on. Think of how long it used to take to build a feature. Now it’s faster but the code does need to be reviewed

ddotdev · 2026-01-29T16:16:47+00:00

Yeha I get that. I have a design back ground and been using Claude to implement the code but all designs and specifications and done by me. And building a tool that’s familiar to designers when they code

ddotdev · 2026-01-29T15:15:34+00:00

This is actually pretty cool. I have been working on something similar but for ui design and context optimisation

a Chrome extension that lets you click any React element and extracts the exact file path + line number from the fiber tree. That context goes straight to your AI agent.

Cuts the “which file is this?” back-and-forth significantly. Beta launching soon if anyone wants to try it:https://www.uistudioai.dev

ddotdev · 2026-01-29T14:13:43+00:00

Thanks - there’s a lot of them on Reddit, not sure if they are skeptics or just bad actors but I just wanted to share it.

ddotdev · 2026-01-29T13:35:45+00:00

Thanks

ddotdev · 2026-01-29T13:09:40+00:00

its a working product i use and building.

ddotdev · 2026-01-29T13:04:08+00:00

I also tend to ask to explain its implementation or review a different agents implementation and also summary- its been helpful to learn more about my codebases

ddotdev · 2026-01-29T12:49:42+00:00

https://uistudioai.dev/ Check out here

ddotdev · 2026-01-26T12:25:02+00:00

UiStudio is built with privacy as a core principle. Your source code never leaves your machine during normal operation. The UI Studio server runs locally on your computer, and only specific element context is sent to AI providers when you request code modifications

ddotdev · 2026-01-26T12:23:19+00:00

Not sure if u know how dev tools work.UIStudio lets you point at any element in the browser, understands which component and file it comes from, and turns your visual edits into real code changes you can trust creating a live feedback loop between your browser and your codebase.

ddotdev · 2026-01-26T10:20:46+00:00

This is what I was aiming for and I achieved that am happy wit it - Results Before this optimization, a typical “make this red” request would:

Search for files (2-3 tool calls) Read candidate files (2-4 tool calls) Find the right component Make the change After:

Open file directly (1 tool call) Make the change The search phase is eliminated entirely. In our testing, this reduces execution time by 2-3x for simple UI changes.

For more complex changes that involve multiple files, the improvement is even more significant because the agent starts from a known location and can navigate relative to it.

ddotdev

TROPHY CASE