Vibe Coding Best Practices
Hello everyone, I am dabbling in "Vibe Coding" and wanted to know if anyone has any advice or best practices?
I have used Cursor for a while, but have just started to use Claude Code to take a more hands-off approach. I am liking it so far for getting the general layout and functionality, and then I go in to clean up and finish the work. I have also used some MCPs, but I am looking for more!
All advice is appreciated. Thanks in advance!
32 views
Replies
I do not use MCPs at all. I use Claude Code, Continue CLI, Qwen Code, Gemini CLI all with git and github directly on command line. They use commands very well. My workflow is git and github based, easy to go through tasks in branches, git worktrees, CI pipelines, etc. I barely see the code these days.
Feel free to poke at the repos: https://github.com/brainless, happy to share anything I can help with.
@brainless Very interesting, thanks for the advice! Curious, are you letting the AI actually make the commits and push to GitHub? And if so, how often do you need to go back and manually fix the code?
@averytribbett I do not manually fix code anymore, except for really rare occasions. It is very rare. To give you an idea, I launched my blog (entirely re-written, imported old data), a micro-SaaS and now building a complex product. Thousands of lines of Rust, TypeScript, working. I have not touched more than 10 lines across all these myself. I know the context well, you can say it is my muscle memory from being an engineer for 16 years. But it was my challenge to myself to not edit code manually for the last 3+ months.
Each project on GitHub has CI workflows. GitHub Actions workflows are also vibe coded. So are deployment scripts. Then I generate scripts to test the state of pipelines or servers. The basic idea is to distill the LLM knowledge into test-able code. This is the core thesis behind my own vibe-coding product.
@brainless Very interesting! Thanks for the advice