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?

Hi, I m an app developer who s shipped many projects the old-school way (hand-coding) for over a decade. Recently AI tools have exploded - speeding up my production like crazy.

What s happening:

- Idea to MVP: Creators focus on ideas while AI writes most of the code.

Here's my hacked-together, messy, voice-based dev environment:

1. Voice-driven loop with screen-shotting so the LLM in the loop can see what's in my terminal and editor. The prompt varies depending on what I'm trying to drive with this loop.

2. A few tool definitions that give read access to files and URLs.

3. A tool the LLM can send a block of output to that generates keyboard events, so the LLM can drive any editor/terminal.

4. A separate process watching a directory and constantly making LLM-driven git commits. (git autosave).

I have some pieces of this running most of the time. But I'm lazy, and doing other stuff, and I also try to use a variety of editors and tools, to see what's good lately. Which ... no stability, so my hacked-together stuff is always broken.

I don't want to replace @Windsurf / @Cursor / Claude code. A seriously good agent and expert-system dev toolkit is a lot of work.

Lately it feels like every week there s a new AI-powered SaaS launching.

Same landing page formula.
Same promises.
Same 10x productivity pitch.

And what s interesting is the number of products keeps increasing but I m not sure demand is increasing at the same rate. It feels like we re repackaging the same value just slightly different positioning.

New UI.
Different niche angle.
Built for X .

I've never coded. Not a single line. But I m tired of just watching cool ideas fly by. So here I am turning a wild idea into something real with AI

as my co-pilot.

My toolkit? ChatGPT, Cursor, Replit.

Hey everyone,

I don't actually like using the term "vibe coding". We've been software developers for over a decade ,are not one-shotting features, and have a very opinionated and strict dev process.

I don't have a CS degree. Never shipped a product. Never started a company. One month ago I didn't know what a Next.js route was.

I built Four-Leaf.ai, an AI career prep platform with voice mock interviews, resume tailoring, and negotiation coaching. It's live, it has users, and I launched it on Product Hunt today.

We now look at actual code less and less. What does your developer experience look like now that we are getting closer to a non-IDE world? I am using @Superset and am loving it so far. In my corporate job, I have 10-15 repos going at once and it's all super organized. What are you all using?

Might anyone have some open URLs of their Vibe coded prototypes on Lovable / V0 / Bolt / Figma Make or Claude Code? I'm looking for some prototypes without logins to test a new version of our product which we'll be announcing next week. I'd like to check it on some existing Vibes.

Bonus points if you have a task for me to user test for you, I'd gladly share feedback.