Video yükleniyor...
Video Yüklenemedi
Can your vibe coding tool do this?
57,909 görüntüleme • 1 yıl önce •via X (Twitter)
37 Yorum

Spoiler alert, it can't.

Because it's really really hard to do.

Superb 🚀

Abu!!

Any chance to implement something like "copy format" functionality? Let us say I have a component with 3 divs and I edited border and corners and background colour of one doc and I want to apply those changes on the remaining 2 divs. Probably not possible/too complicated... However should there be a way then the next logical step would be copying formats between components on canvas...

I like this, worth experimenting

I am a MagicPath pro user and I hope I find time to give you more "tips' like this. It is very difficult to implement - I did the same now in my project when I was setting in react all settings to edit from frontend SciCharts design on the fly... It was a nightmare. Really root for you to succeed with Magic Path!

damnnn no it cannot

Let's gooo!

Wow

Insane, when the Figma integration planed? This year?

Oh this is cool. Direct editing within the vibe code/prompt interface.

Yep, and what you get is React code ready to use. We are truly the only product (@MagicPathAI) that allows this level of control with AI. And every time you save a change, we keep a full version control history of your designs.

love the inline component edit mode

fantastic!!

Dope to see that in realtime With stuff like stagewise and Irfan you have a close second

This is what @Replit needs - @darshkpatel

I will try on the weekend

Ooh that’s clean

Looks slick—like Figma with AI—but I’m still wondering how stable it is and whether it’s truly faster end‑to‑end; lately I’ve found starting from solid templates and straightforward edits often beat AI tools in real workflows, where overhead and unpredictability slow things down.

I can step outside my door and look at this myself :-)

Appreciate that it definitely requires desktop, but I’d like to see website from mobile at least to check features and pricing

not sure how you see this, but from a designer’s perspective, design output is an iterative and exploratory process. If this process can’t be carried out directly within the product, it creates a strong sense of insecurity and lack of direction.

You are right, it cannot! I mean…well…it would be ugly at the beginning and you probably would spend quite some time to fine tune it (in English). However, most importantly, you probably won’t be able to maintain it at production state. 😅🤣 The code is so ugly, never look there, adding the features on your own - good luck 🍀

Are we able to see our original prompts yet? When I create a new component, I can’t see them after the fact.

maybe in 10 years, but it is still easy to distinguish an ai generated front vs the human master piece

Yes

@chiefbuidl who's gonna tell him?

Hey man, You should check out my platform now! It’s fully vibe-coded using @v0. Generate high-end UI using prompts and export Figma editable. I deserve your subscription to my platform :)

thread builders are underrated for pre-launch buzz. visual preview = higher engagement. tip: if you're building this, add scheduling + auto-publish to twitter api. canva tried this but ux was clunky. also consider templates—most people struggle with thread structure. give them 'product launch', 'story time', 'how-to' frameworks. speeds up creation, increases usage frequency

Is this only for designing and static data only ? Or truly meant for building UI ?

Literally v0

Yes actually

Is this not figma make?

What's the base for the components, shadcn or something? Everything generated will look the same - basic customisation won't change that...

This is impressive Pietro, and I agree, they can't yet! What's the process to move from those beautiful UIs to a "semi" functional - vibe coded solution? Exporting and importing into Cursor? I am curious, because I find myself more and more designing with an AI first approach, where I am building advanced dirty prototypes... not production stuff, meant to lock in UX and flows... and then exporting single screens from Figma Make to Figma to polish... So the approach to MagicPath would be different... but without any layer of logic I find myself strugling to find a way to use it. I may be an edge case, or not the primary audience tho.

review it :)
