working theory for a new vibe code workflow:
57K followers
14,952 views
28 Comments
Comments from the original post on X (Twitter)

@frankdegods
it’s so rare to like a fully stylized design from any of the models i’ve religiously been saying “make basic html, no styling, no formatting, barebones” for every inital ui/ux i make now but most of stuff i make is for scripting/internal tooling so maybe different
16 likes

@0xDesigner
im still using figma for that
7 likes

@MAZM0L
Similar Workflow 1. create a proof of concept in v0 2. move to github and clone in a local repo 3. Use Cursor to expand and work on it + use that to check code generated to clean up code 4. Publish using Vercel
3 likes

@rabbabAnsh
separating g frontend from backend even if its a simple folder really helps alot
1 like

@SankalpArora03
This is exactly I start the projects
1 like

@buildwithparas
the real step 6: stare at 10 variations and pick the worst one somehow

@0xDesigner
nope. ask for 10 more.
1 like

@hoffz_eth
That's how i started and got my bf to vibecode! Really like this workflow

@brianchew
I would just use @cursor_ai or @ManusAI (if you’re less technical) to do this

@jmickelin
Very interesting! Been thinking a lot on this but also how you can add integrate v0 / lovable as concept designs in issue tracking like linear

@GLHFbuy
this looks like a more structured approach could really help streamline your workflow.

@Zevweb3
v0 + local repo = design freedom

@letrplB
wait did you not separate backend and frontend before?

@0xDesigner
nope
1 like

@letrplB
can be a pain to remind the agent to keep the business logic out of frontend, but things become so much more stable during fast iterations.
1 like

@binji_x
curious how you rate this over figma make

@0xDesigner
figma make is great i just cant do anything with it when i'm "done" it's just stuck in figma

@binji_x
ah I see. do you know @julianweisser by the way? he has a program you may really like
1 like

@0xDesigner
@julianweisser followed. thanks bub.

@talondragon000
I seriously need to start separating my frontend from my backend from my web3 contracts for this reason. 🫠






