I made a quick video showing people how to get started vibe coding using a powerful method called "BMAD". This is the first lesson in a new course. More lessons to follow!

Wes and team, This link below doesn't work. Does anyone have the txt file they can share? https://github.com/bmadcode/BMAD-METHOD/blob/main/dist/teams/team-fullstack.txt

Hi everyone, By all means, I don't want to self promote but lots of people in my LinkedIn network showed interest (though Reddit seems to be having a different opinion 😄), hence thought worth sharing. I found a way to make apps built with Claude code at least as pretty as lovable apps (arguably depends on what you consider pretty 😉). https://www.reddit.com/r/vibecoding/s/hM9PUG078x Let me know if you have questions. Cheers, Mario

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.

I kept seeing MVPs take weeks, so I tried a tighter loop. After 20+ Lovable builds and $29k in a few months, here’s the flow: Day 1: problem → 1-page PRD → static skeleton Day 2: 1–2 core features (tiny scope) Day 3: auth in 2 prompts Day 4: Stripe + SEO basics Day 5: clean deploy + demo PRD kickstart prompt (use Perplexity first): You will create a PRD I can paste into lovable.dev. Ask 5–8 clarifying questions in one list. Wait for answers. Then output: 1) ~50-word summary 2) Pages with exact routes + 1-line purpose 3) 6–8 user stories + 1 acceptance check each 4) Data objects (names + behaviors; no fields) 5) UX flow (happy path + empty + failure) 6) Two-week plan 7) Copy (3 hero, 5 microcopy) 8) Skeleton build prompt Constraints: non-technical, consistent route names, no DB fields. Stripe prompt (clean template): Add Stripe subscriptions and a simple paywall. Plans: - Basic $29/mo - Pro $290/yr Requirements: - Update subscriber status in real time - Lock premium pages until subscription is active Two quick tactics: Verify skeleton with a Route Snapshot that matches your PRD character for character. If anything drifts, restore and rerun smaller. Debug faster with “investigate first”: list 3 likely causes and how to confirm each, wait for approval, then implement. If this is useful, I can share the full checklist and the exact prompts I run (free Notion). If mods are cool with links I’ll drop it in the comments, or DM me “loop” and I’ll send it. I also host a small weekly Q&A where we swap prompts and unblock each other.