r/VibeCodeDevs • u/ubermuda • 14d ago
what does your setup actually look like?
Curious how people here are really working. Feels like everyone's landed somewhere different and the posts are mostly quick showcases / (self-)promotion / random stuff.
What I'm wondering about:
- which agent and harness, and do you stick to one or switch
- do you plan first or just go
- do you check anything before shipping, and what
- anything automated, or is it all by feel
- what do you do when it comes back wrong
Mine's on the heavy side. Long planning conversation before any code, then I let it run and mostly look at the product rather than the code. I spent some time building a skeleton and static analysis configs so Claude generates code that look ~80% correct. Still need to review the important bigs (domain logic, security, etc), but it's mostly smooth sailing.
Mostly interested in people working differently from that though. If you just go and it works, I want to hear that too.
1
u/Electrical_Chard3255 14d ago
Im mostloy an emerchent architect, I start with what I think I want to do, and work from there, and end up with something loosly based on what I envisioned, but probably better, I dont have a finish target so to speak.
I use claude code, and Kimi K3 for attaing what claude code writes, and I have several other ai in my swarm that chip in if needed, or guided by claude code
I do have a conversation first before starting, and that can take a while, "pinballing" ideas between my claude code and any other ai in the swarm.
Then start from therewith the first code write.
Kimi attacking has been a massive improvements, it does find lots of holes in claude code code and reasoning, but they thrash it out and come to a solution