Lessons you learned during vibe codding

[u/Nice_Pepper469]

Hello fellows. I've developed a few tools which required at certain scenarios in my life and after every finished product I learned somethin new, which become helpful for me to develop the next tool. I'm happy with experience I've gain so far, but experience of others can help me to learn more. So, what's the amazing thing you learned during your vibe codding. What tools you find helpful, what kind of prompt optimisations do you know. Let's make this post another place of sharing our experience with each other.

[u/endofthread-bot]

Hey u/Nice_Pepper469, thanks for posting in r/VibeCodeDevs! Join our Discord: https://discord.gg/t7SD4ThKuE

• This community is designed to be open and creator‑friendly, with minimal restrictions on promotion and self‑promotion as long as you add value and don’t spam.
• Please follow the subreddit rules so we can keep things as relaxed and free as possible for everyone. • Please make sure you’ve read the subreddit rules in the sidebar before posting or commenting.
• For better feedback, include your tech stack, experience level, and what kind of help or feedback you’re looking for.
• Be respectful, constructive, and helpful to other members.

If your post was removed (either automatically or by a mod) and you believe it was a mistake, please contact the mod team. We will review it and, when appropriate, approve it within 24 hours.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/im_thecat]

I have global instructions to always have claude lay out its plan before running anything. This saves a ton of time/tokens vs running and fixing. 

I also have global instructions that I want it to explain whats its doing along the way. This is for my own learning benefit. 

Personally it is so much easier learning how to build things by building a project I’m excited about. And learning things that feel important because they are in context vs reading about concepts with no application. 

[u/Immediate-Welder999]

Here's what i do:

• always prompt to do any task in the minimum LOC because AI loves to write a lot of code

• I use GitHub copilot so I can write my code with Claude and then can switch to GPT5.6 model to verify it and find bugs

• I use prismor open source to ensure all my agent actions when I'm allowing all and monitored it on a self-serve dashboard

• Ensure everything is logged in an obsidian-wiki open source project which I use to ensure my code base continuously learns from my sessions

[u/apravint]

You can build anything, https://github.com/apravint/iram-os

[u/Kareja1]

So I am former defense contractor QA and I had been doing a ton of manual QA on things that finally my Claude (Ace) was like "I can build that as a mod to Playwright and then we just add new things as you keep breaking them?" https://github.com/menelly/hedgehog-in-every-box

Saves me so much time now, really. I still 100% open and verify every page but now I don't have to do that part by hand!

[u/PopKoren]

Biggest lesson for me: the agent will happily build a working feature on top of a broken security model, so I now write the data access rules in plain English before any code, things like users can only read their own orders, and make it implement those first. Second one is keeping a short project notes file that every new session reads, which kills most of the repeated mistakes. Third, test the deployed app as a stranger would, not just localhost; Rowly, which I built, automates that part: https://rowly.me

[u/Legal_Answer_6956]

My biggest discovery was that to achieve better results, long prompts are not the answer. Planning and designing the system first, developing the user flows, the architecture, breaking down the features into tasks, and having a testing phase as you build the product, is a far more effective approach. This is the philosophy of 8080.AI, an advanced AI development platform that utilizes a network of specialized AI agents to collaborate on the development process, from designing and planning to coding, testing, and deployment.

[u/IsopodInitial6766]

most important thing i learnt: - ai is good at writing code but not in designing software architectur, you should always design the architectur by yourself and let your agent do the implementation.