Raunak Singh Johar

Few months ago (like everyone else) I also got overwhelmed with all this vibe-coding happening around me, being a developer myself I got a little FOMO too I have personally built a bunch of tools using "pure" vibe-coding.

It took me a while to understand that one of the biggest challenges of vibe-coding is the back & forth with AI - which can save or burn a huge amount of your time. I got stuck with fixing and recreating code bugs and fighting with the leaks that AI generated for me.

My first product - which was a simple resume parser and enhancer took around 3 months to build for the same reason. It failed badly - because I sucked at marketing.

With the second product that I launched which was a no-code portfolio website builder (Fllaunt AI) took around 2 full weekends only!

about to Launch a product for creators after building for a few weeks to months.
Started as a way to get into vibe coding and just got real useful real quick lol.
But the goal is still that - mix my skills and knowledge as an engineer with the good parts of AI coding.
So i learned a few of what to need and have

• Claude.md file

• best coding practices section

• pretty heavy compartmentalization & file structure separation

• certain ways to prompt

• ask for implementation plan before telling it to code

But i feel like all i learned is about directing prompts - im wondering...

what are you guys finding are the best .md or deeper ai vibe coding tricks that are helping you save time? be more efficient? debug ai less or help it get it right the first time? whats your vibe code tips and tricks?