2h • General Discussion 💬
Quick share for anyone building with AI 👇
If you’ve tried vibe coding and felt:
- things break randomly
- AI overcomplicates simple features
- you spend more time fixing than building
…it’s not you.
I kept running into the same issues until I started following a few simple rules when working with AI.
I’ve written down 8 rules for Vibe Coding without frustration and dropped them as a PDF here.
Very short version 👇
1️⃣ Let AI plan first (README + milestones)
2️⃣ Keep the tech stack boring
3️⃣ Give AI rules + docs upfront
4️⃣ Ask for the plan before asking for code
5️⃣ Ask for options, pick the simplest
6️⃣ Break work into tiny, testable steps
7️⃣ Use screenshots to give context
8️⃣ Test after every single change
The biggest mindset shift for me was this:
👉 Treat AI like a smart but overconfident intern.
Clear direction + small tasks = way better results.
If you’re using tools like Cursor, Claude, Lovable, n8n, etc., this should save you a lot of pain.
Curious to hear from the group 👇
What part of AI coding frustrates you the most right now?
Planning? Debugging? Over-engineering?
Let’s compare notes 👀
If this was useful, let’s connect on LinkedIn 🤝
I regularly share practical stuff around AI, automation, and vibe coding.
2
1 comment
Quick share for anyone building with AI 👇
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
1
+10369
2
🔥
+6012
3
+3662
4
+2852
5
🔥
+2444
Powered by