A solo builder shipped VibeCoding.is — a directory site where vibe coders submit their projects for community review. The site itself was vibe-coded.
The pitch is simple: a catalog of real, usable projects built primarily through AI-assisted prompting, with reviews and data points attached. Submission requires:
- Project details and description — including how much was “vibed” vs. built with other tools
- A screenshot or image
- A live link to the working project
- Email confirmation via a code
No login wall, no lengthy onboarding. The creator explicitly asks that submissions be active and usable — not mockups or half-finished repos.
The interesting constraint: projects don’t need to be 100% vibe-coded. The creator notes their own projects use “various degrees of vibed and other tool sets, depending on the needs.” That honesty matters. Most shipped vibe-coding projects involve manual intervention at some point — a CSS fix here, a database schema tweak there. The description field is meant to capture that nuance so reviewers understand what they’re actually looking at.
NOTE
The site is in early submission phase. The creator is actively requesting feedback on bugs and UX issues, so expect rough edges.
This fills a gap. Right now, vibe-coded projects get scattered across Reddit threads, Twitter posts, and Discord channels. There’s no single place to browse what people are actually building and shipping with AI-first workflows. Product Hunt doesn’t distinguish between traditionally coded and vibe-coded projects. GitHub repos don’t show the finished product running live.
VibeCoding.is is accepting submissions now. If you’ve shipped something with Cursor, Claude, Bolt, or any AI-first workflow, it’s a low-friction way to get eyes on it — and to see what the rest of the community is building.