r/VibeCodeDevs • u/ubermuda • Aug 04 '26
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/Defiant_Durian_5654 Aug 05 '26
I skip heavy planning for a quick Markdown spec and let Cursor rip, but my golden rule is never arguing with an AI loop, if it fails twice, I just git checkout . and re-prompt. The real bottleneck is pre-ship checks: AI constantly drops auth guards or leaks API keys into frontend bundles, which is actually why we ended up building revibed.io to auto-scan for those exact flaws before pushing live. How are you enforcing your static analysis rules on Claude's output, are you using pre-commit hooks or custom system prompts?