[hdhdhsjsbdh]

Interesting that this thread mostly consists of people sharing vibe-coded projects they themselves made, not people sharing other people’s projects that they’ve found useful. The latter would provide higher confidence that the project is actually impressive. It’s the IKEA effect for software.

[patch_collector]

Vibe coding is a great for 'home cooked software.' Lots of people are making tools that fill a particular need for themselves.

https://www.robinsloan.com/notes/home-cooked-app/

As for sharing a tool that someone else has made that's useful, I don't think most people are advertising that the tools they've built are vibe-coded, so it would be hard to know what to share.

[crazygringo]

How would people know if someone else's project was vibe-coded?

Sometimes that will be in the readme, but there's no reason it has to be. And most people aren't going to be checking anyways.

[alyxya]

I think Claude Code itself is mostly vibe coded if you consider that impressive. In general I’m not aware of any vibe coded projects with a substantial amount of iteration put into it rather than being close to one shot, which is why I shared mines. Any project someone can one shot is also something anyone else can vibe code for themselves.

[seattle_spring]

> I think Claude Code itself is mostly vibe coded

What definition of "vibe coding" are you using here? I seriously doubt Claude Code was made "mostly" (or even "partly") by telling a prompt what they want, and accepting the output when it looks functionally acceptable without regard to how the code looks or works under the hood.

... Which is what "vibecoding" is.

Vibecoding != AI assisted/agentic coding