Skip navigation
working theory for a new vibe code workflow:
0:00 / 0:22

working theory for a new vibe code workflow:

120 likesDownloadOriginal post

14,952 views

working theory for a new vibe code workflow: 1. create a proof of concept in v0 2. move to github and clone in a local repo 3. use as ref for agent planning 4. create a backend directory to test API plumbing 5. create a frontend directory to prototype iteratively this way you can repeatedly rip apart the frontend for ideation without worrying about breaking changes to the backend. i really like asking for an open ended "job to be done" (i.e. place a bet with a single tap) with 5-10 variations to feel. it's the modern day wireframing. it's still UI slop but i can get ideas in my head out faster and reveal design shortcomings before polishing or worrying about making components functional. and because the v0 prototype gets you to functional ai features and backend integration fastest, you have both a technical and conceptual reference to use in your agentic planning so your v1 is more predictable with minimal effort.

28 Comments

Comments from the original post on X (Twitter)

  • Frank's profile picture

    @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's profile picture

    @0xDesigner

    im still using figma for that

    7 likes

  • MAHIR's profile picture

    @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

  • ansh 🧢's profile picture

    @rabbabAnsh

    separating g frontend from backend even if its a simple folder really helps alot

    1 like

  • Sankalp Arora's profile picture

    @SankalpArora03

    This is exactly I start the projects

    1 like

  • Paras's profile picture

    @buildwithparas

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

  • 0xDesigner's profile picture

    @0xDesigner

    nope. ask for 10 more.

    1 like

  • jubs's profile picture

    @hoffz_eth

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

  • Brian Chew's profile picture

    @brianchew

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

  • Johan Mickelin's profile picture

    @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

  • abuy's profile picture

    @GLHFbuy

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

  • Zev's profile picture

    @Zevweb3

    v0 + local repo = design freedom

  • bstn's profile picture

    @letrplB

    wait did you not separate backend and frontend before?

  • 0xDesigner's profile picture

    @0xDesigner

    nope

    1 like

  • bstn's profile picture

    @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's profile picture

    @binji_x

    curious how you rate this over figma make

  • 0xDesigner's profile picture

    @0xDesigner

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

  • binji's profile picture

    @binji_x

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

    1 like

  • 0xDesigner's profile picture

    @0xDesigner

    @julianweisser followed. thanks bub.

  • TalonDragon000.shefi.eth 🐉💜's profile picture

    @talondragon000

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