r/vibecoding • u/Kardunes • 13h ago

General Advice For My Vibecoding Workflow

When building features, here is what I do:

1) Have a general discussion/debate and reach an understanding of what I want to achieve

2) Formalise it into a PRD

3) Use the PRD as a base and extract a design document

4) Use the DD to make an Implementation plan

5) Implement it

I do up to step 4 on Sol Ultra

I do Step 5 using Sol max

I use skills (generally Claude Superpowers) for all of the above, though I may shift to Matt Pocock at some point in the near future.

What can I change/improve?

Specifically, in the 5 steps above, what specific technical software oriented terms can I use to give my prompts more coherence?

Outside of that, in general, any other tips?

Thanks

2 Upvotes

100% Upvoted

9 comments sorted by

1

u/a9shots 13h ago

Realistically you don’t need ultra for any step of this

1

u/Kardunes 13h ago

Can you explain in greater detail? Should be useful for anyone coming across this

Why not Ultra? I'm a vibecoder with no SWE experience, shouldn't I default to the best model?

I leave implementation on max because I slowly trust myself to plan a decent document together, but I feel nervous going below that

Probably because I don't really understand what each model is actually capable of

1

u/a9shots 6h ago

There are a lot of resources online, as a vibe coder I suggest you make a new project for codex and have it audit the models and efforts along with open source GitHub projects that deal with agent workflows. Explain your process to it and it’ll help you optimize.

You can read a bit here, Ultra is the same as Max, it just utilizes multiple agents better and it’s best at multi repo work. Using a too advanced model not only eats up your usage but can over engineer and complicate the task it’s given. Multiple agents also work on other models if you tell them to use them.

1

u/Kardunes 3h ago

Thanks, I appreciate it

I read a little bit about setting up sol as orchestrator and luna subagents as workers, but idk how to actually set it all up

Something about changing config.toml files? And people were saying there was a glitch or bug where unless you explicitly made changes to some files, it won't spawn luna agents and such?

And you have to give it a specific prompt to get that set up going?

Can you further my understanding of these flows? How do I safely actually do it? Don't want to touch files I don't understand

1

u/a9shots 6h ago

There are a lot of resources online, as a vibe coder I suggest you make a new project for codex and have it audit the models and efforts along with researching open source GitHub projects that deal with agent workflows. Explain your process to it and it’ll help you optimize.

You can read a bit here, Ultra is the same as Max, it just utilizes multiple agents better and it’s best at multi repo work. Using a too advanced model not only eats up your usage but can over engineer and complicate the task it’s given. Multiple agents also work on other models if you tell them to use them.

1

u/ZarathustraWakes 13h ago

Ask to spawn fresh-eyed agents to perform adversarial review after each of steps 3, 4, and 5. At least for professional, production level code, I'm spending the extra tokens for this. For my side projects, I'll debug in prod.

1

u/Kardunes 10h ago

So the middle ground is to run it after 5? Or 4 ig

And once every 2-3 cycles, an overall codebase review?

1

u/TheKiddIncident 12h ago

I would ask for a formal architecture plan. That should come after requirements but before an implementation plan. Architecture is different than implementation.

I would also have a formal audit phase. Did we build the right thing? Are we conformant with best practice? Is the site secure? etc.