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.

Currently playing around with @bolt.new after being inspired by @gabe and building a bunch of mini apps, mainly for fun. Haven't pushed any to production yet but so far I'm enjoying it bar the odd hiccup where I have to roll back a few times to fix a stubborn error.

I've also looked into @Lovable and it seems pretty cool but wanted to see what people had to say about it. Is there any reason to pick one over the other and which one have you settled on?

Came across the recent Claude Code leak from Anthropic, and what stood out wasn t the leak itself, but what it revealed about how these systems actually work.

• A source map file accidentally exposed ~500k lines of TypeScript

• Turns out Claude Code is basically a multi-step prompt orchestration system, not some mysterious black box

• Includes things like:

  • layered prompt pipelines ( prompt sandwich )

  • fake tools to prevent model distillation

  • simple frustration detection (regex for rage prompts )

• Even hints at future features like background agents and persistent memory systems

What s interesting is this:

It kind of confirms that the real product layer in AI isn t just the model it s everything wrapped around it.

Which raises a few questions:

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?

I'm what you might call a gringo vibe coder.

No dev degree. No traditional background. Just me, Cursor, Claude, and AI... figuring things out together.

Rick Rubin said it best: "In the past, for music, you had to go to the conservatory and study for years... then when punk rock came along... if you had something to say, you could say it." He calls vibe coding the punk rock of coding.

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.

I work at an early stage startup and I'd estimate 70-80% of our codebase is vibe coded (510k lines). To be clear, it's not 1 shot "build this feature." More like, "implement get_slim_documents for Jira in the exact same way we did it for the Confluence connector."
Comfort with AI coding tools is actually something we gauge during interviews/work trials. Looking at our peer companies, it's exactly the same.
My hypothesis/assertion is that companies founded ~2022+ are fundamentally intertwined with "vibe coding." In 5 years, programming will connote vibe coding more than it will connote non-AI assisted work.
Am I crazy? Pigeon-holed in the SF startup world? Naive? Would love to hear more thoughts/diverse perspectives on this.

I've been having a lot of fun exploring AI and using tools like @Cursor, @bolt.new, @Lovable, and @Warp to learn how to build and make some apps for myself! I'm also noticing a tremendous amount of growth in folks creating their own apps using these same tools which has me wondering... if a company wanted to acquire someone's app or tool that was built via vibe coding, would it matter how it was built? Does the method of how it was built impact the valuation?
In my idealistic eyes, I'd like to think it doesn't. As an acquisition is often much more than just the tech but also the user base, brand, and even team behind the product. If anything I think that acquiring a product that has been "vibe coded" and putting them into capable engineering hands would only enhance the product...or a least make the code base cleaner.
I also believe that talent that is able to create stunning products with AI is currently a small percentage of folks, and that companies should be investing in acquiring that talent (either independently or via product acquisition) so that they can stay ahead in innovation while learning how to implement AI tools more efficiently in their orgs.
Very curious to hear what you all think!

14 days to build. Voice input, AI extraction, relationship intelligence layer , the whole thing.

The idea: walk out of any important conversation, vent for 60 seconds, and let AI pull out everything that matters. Prices quoted. Commitments made. The personal detail they dropped in passing. All of it structured and surfaced before the next conversation.

Here's what surprised me building this:

Voice input is a completely different product than text input

Obviously there is a ton of hype around OpenClaw and everyone rushing to get Mac Minis and set it up. But what happens now that Anthropic has created a seemingly more secure and easier to set up version of OpenClaw with Channels?
Do you think OpenAI will adapt quick enough and evolve OpenClaw to be at the forefront of the localized agent space? Or will Anthropic run away with it? Would love to hear what you all think.
Btw, our current operation at Honestly is using Claude Code Channels, check out our socials accessed through our #4 PH rank to follow along with how we've been using them!