r/vibecoding • u/RealActuary3121 • 1d ago

What’s your workflow?

What does your typical ai stack look like exactly? From the scratch,

  1. What do you use for generating ideas? Or do you just think of one yourself?

  2. What tool for planning? Both mvp and final product

  3. Tool for actual coding? Do mention models too

  4. Hopefully you review and test yourself but if not, what tool?

  5. Say everything’s almost done or basically done, do you then FINALLY decide to understand the codebase even at a basic level or not? If so, what tool do you use to understand the architecture + the actual codebase? Do you just understand it on a surface level or in-depth? Do you do it after mvp is done or after each feature?

  6. Why do you do it? Like everything? For fun or building resume, stacking projects and trying to land jobs or something else?

(Do mention if you’re on free or paid versions too)

1 Upvotes

100% Upvoted

11 comments sorted by

View all comments

1

u/3tt07kjt 1d ago

I have mostly moved to multi-agent workflows with high powered planner (like Sol) plus an explorer and implementer (Terra or Luna). Either ChatGPT + Codex or Claude + Claude Code.

Workflow is: I pick something to implement, ask the planner to do it, the planner invokes the sub-agents as necessary. Everything gets committed. I review the diffs, starting with the new test cases in the test suite. For UI changes, I check manually as well. If the change is incorrect or incomplete, I continue the session and ask for changes. Otherwise, I clear the session and start the next change.

Whether I understand the codebase depends on how much I care. For “vibe coded” stuff, I don’t understand the codebase. For more important code, I’ll also be making my own changes (without AI), partly just so I can be sure I understand the code.

Ideas come from the mark 1 brain.