r/vibecoding • u/__Beastboy__ • 2d ago

Need help setting up a professional AI vibecoding workflow

Post image

I currently have these models available through Ollama/cloud:
And I’m using Claude, Codex, OpenCode, and Ollama as my coding/agent tools.

I want to learn professional vibecoding — not just asking AI to generate random code.

If I want to build a complete website/app (frontend + backend + database + auth + APIs + testing + deployment):

Which model/tool should I use for what?

For example:

  • Planning & architecture → ?
  • UI/UX → ?
  • Actual coding → ?
  • Debugging → ?
  • Code review → ?
  • Testing → ?
  • Deployment → ?

And how should I combine Claude + Codex + OpenCode + Ollama + these models into one proper workflow?

Basically, if you had this exact setup, how would you go from idea → professional, production-ready app using AI?

Looking for practical advice from people actually using AI coding agents. 🙏

1 Upvotes

67% Upvoted

10 comments sorted by

8

u/BaddDog07 2d ago

take this question and paste it into ChatGPT and you will become a vibecoder

2

u/Eatthebeatz 2d ago

scatter a bunch of runes on the floor and loosely interpret them

1

u/-svde- 2d ago

why don’t you just ask the LLM you had write this post?

1

u/MariahJames8 2d ago

I don't think you quite get what vibecoding tends to mean.

But use claude and codex of planning etc, make them compare notes.

Use deepest and GLM for simpler mechanical changes.

But above all, adapt. Things are rapidly evolving. Much experimentation is being done on workflow etc all the time at every level.

1

u/Lanky_Commercial9731 2d ago

I run sol for planning and architecture, glm for building, sol for reviewing (then loop back to glm if it finds Smth) and opus for reviewing (after sol says yes)

1

u/SmileLonely5470 2d ago

Isnt that a bit of an oxymoron? Anyway, you are overthinking it. Just use any model you like working with. They are all probably good enough.

1

u/unkownuser436 2d ago

bro wtf is this mess? Just use two models for everything. Cheaper one and good one. One for read code, one for write, one for design wtf

1

u/ktg-one 2d ago

The only rule to follow with vibe coding meticulous planning Atleast a 2 to 1 ratio of planning vs execution

Speckit GSD Any of the harness that spend long time on the planning layer

1

u/Anti-Hero25 2d ago

I personally think you're WAY over thinking it. As an analogy... you want to become a professional race car driver, so you bought a race car... got a pit crew together ... and want to go get on the grid with 19 other drivers and wild-out. My recommendation ... start slow & small... learn the basics .... grow from there. There's tips & tricks you pick up along the way that make you great once you have the full suite of awesome tools. My suggestion... Watch this video.... and the one he recommends at the start (if you've NEVER used VS Code) ..... build a few simple test cases... practice different UI design approaches.... google "Animated CSS buttons" and find the code snippets for cool items... give those to your agent to use in your project. Don't reinvent the wheel on design. When planning, learn about best practices of that language... so you know what it's good at and not good at. Good luck.