I built something that fits right into our vibe coding flow — it’s called AI Diagram Maker. Instead of manually dragging boxes or tweaking arrows, you just describe your system in plain English, and the AI instantly turns it into a clean, professional diagram. Perfect for when you want to vibe create flowcharts, sequence diagrams, ERD etc. No friction, no formatting — just describe → generate → tweak if as needed. I’d love for you all to try it out and share authentic feedback — what works, what doesn’t, and what features you’d love to see next. You can try it free here 👉 https://www.aidiagrammaker.com

I often use Cursor and Windsurf for Vibe coding. When I ask them to fix slightly complex bugs, they sometimes struggle — even after prompts like “think hard” or “fix really” Here’s a trick that works surprisingly well 1. Ask the LLM to only add log lines (no fixes yet) to help debug the issue. 2. Re-run the code and share the log output with the LLM. Ask it to investigate and fix the problem using those logs. 3. Once it’s fixed, ask it to remove all log lines containing your special tag. This approach works consistently — the model can actually reason through the issue better when it sees real log context, just like a human would.