Add Vibecoded Apps

[levz0r]

A curated list of apps and projects built with vibe coding — an AI-assisted development approach where developers collaborate with AI to bring ideas to life.

Reviewed PRs

• #3960 - Add Webhooks
• #3952 - Add Performance Engineering

Checklist

• Has been around for at least 30 days (first commit: November 27, 2025)
• Passes awesome-lint
• Default branch is main
• Has awesome-list and awesome GitHub topics
• Includes Awesome badge next to heading
• Table of Contents
• CC0 license file
• Contributing guidelines
• Curated content (67 entries across 11 categories)

[levz0r]

unicorn

[fdmarcin]

Thanks, this PR follows the guidelines.

One tiny exception is that not all entries in this list are title-cased, but the ones that are not are in the CLI section, so it makes sense.

[springmoments]

Unicorn

[tahayigitmelek]

The current pull request template is incorrect and should be reviewed (see here), as it does not clearly require essential information, making the review process harder.

[webmaxru]

[Nitpick}: The PR body only lists 2 reviewed PRs while the requirement is at least 4.

[levz0r]

[Nitpick}: The PR body only lists 2 reviewed PRs while the requirement is at least 4.

When this PR was issued, the requirement was to review 2 other PRs.

[sindresorhus]

Top description describes the list.* The blockquote reads: > A curated list of awesome apps and projects built with vibe coding… This starts with "A curated list of…" which is the canonical bad pattern. It also contains "awesome" in the description. Replace with a succinct description of the subject, e.g.: "Software created through AI-assisted development where developers collaborate with AI to bring ideas to life."

Empty section. "Libraries & Frameworks" has a heading but zero entries. Remove it or populate it.

Self-promotion without disclosure. Four entries are by the list author (levz0r):

• ASCIIKeyboard (levz0r/ASCIIKeyboard)
• claude-code-statusline (levz0r/claude-code-statusline)
• html-to-markdown-mcp (levz0r/html-to-markdown-mcp)
• Markdown Printer (levz0r/markdown-printer)

That's ~6% of entries. Disclose your relationship.

Entries with no indication of being vibecoded. Several entries describe what the product does but give no indication it was built with vibe coding:

• Nomad List - "Find the best cities to live and work remotely with crowdsourced data." Launched in 2014, years before vibe coding was coined.
• Remote OK - "The largest remote job board with thousands of remote work listings." Also predates vibe coding.
• Photo AI - "Generate photorealistic AI photos of yourself in any setting or style."
• Airweave - "Connect apps like Gmail with AI agents for workflow automation."

Other entries explicitly note their vibe-coded origin ("100% AI-generated", "fully AI-coded", "built with Claude Code"). These entries don't. If they belong in the list, their descriptions should mention how they were vibecoded. If they predate the concept, they probably don't belong.

Entry description describes list contents. Your entry reads:

- [Vibecoded Apps](…) - Apps and projects built with vibe coding, an AI-assisted development approach.

"Apps and projects built with vibe coding" describes what the list collects. Compare with the bad example: ❌ Resources and tools for iOS development. Better: "An AI-assisted development approach where developers describe intent in natural language and collaborate with AI to generate code."

Some descriptions are about the development process, not the app. For example:

• "A fully AI-coded game where not a single line of code was manually written, including sound effects and music." (Crashy Zorg)
• "~20K lines generated by Claude Code" (Context)

The list's theme is vibecoded apps, so mentioning the AI origin is relevant. But the primary description should still be what the app does, with the vibe-coding detail as supporting context.

[levz0r]

Top description describes the list.* The blockquote reads: > A curated list of awesome apps and projects built with vibe coding… This starts with "A curated list of…" which is the canonical bad pattern. It also contains "awesome" in the description. Replace with a succinct description of the subject, e.g.: "Software created through AI-assisted development where developers collaborate with AI to bring ideas to life."

Empty section. "Libraries & Frameworks" has a heading but zero entries. Remove it or populate it.

Self-promotion without disclosure. Four entries are by the list author (levz0r):

• ASCIIKeyboard (levz0r/ASCIIKeyboard)
• claude-code-statusline (levz0r/claude-code-statusline)
• html-to-markdown-mcp (levz0r/html-to-markdown-mcp)
• Markdown Printer (levz0r/markdown-printer)

That's ~6% of entries. Disclose your relationship.

Entries with no indication of being vibecoded. Several entries describe what the product does but give no indication it was built with vibe coding:

• Nomad List - "Find the best cities to live and work remotely with crowdsourced data." Launched in 2014, years before vibe coding was coined.
• Remote OK - "The largest remote job board with thousands of remote work listings." Also predates vibe coding.
• Photo AI - "Generate photorealistic AI photos of yourself in any setting or style."
• Airweave - "Connect apps like Gmail with AI agents for workflow automation."

Other entries explicitly note their vibe-coded origin ("100% AI-generated", "fully AI-coded", "built with Claude Code"). These entries don't. If they belong in the list, their descriptions should mention how they were vibecoded. If they predate the concept, they probably don't belong.

Entry description describes list contents. Your entry reads:

- [Vibecoded Apps](…) - Apps and projects built with vibe coding, an AI-assisted development approach.

"Apps and projects built with vibe coding" describes what the list collects. Compare with the bad example: ❌ Resources and tools for iOS development. Better: "An AI-assisted development approach where developers describe intent in natural language and collaborate with AI to generate code."

Some descriptions are about the development process, not the app. For example:

• "A fully AI-coded game where not a single line of code was manually written, including sound effects and music." (Crashy Zorg)
• "~20K lines generated by Claude Code" (Context)

The list's theme is vibecoded apps, so mentioning the AI origin is relevant. But the primary description should still be what the app does, with the vibe-coding detail as supporting context.

Thanks for the detailed review! I've addressed all the feedback:

• Fixed the top description — removed "A curated list of awesome..." pattern
• Removed the empty "Libraries & Frameworks" section
• Added a Footnotes section disclosing maintainer-authored entries
• Removed entries with no clear vibe-coding origin (Nomad List, Remote OK, Photo AI, Airweave)
• Updated the entry description to describe the subject, not the list contents
• Rewrote descriptions that focused on process over product (Crashy Zorg, Context)

[kimimgo]

Review: Add Vibecoded Apps

The topic is timely and the maintainer has been responsive to feedback. Here's what I found:

Format & Structure (mostly good)

• ✅ Awesome badge present and linked correctly.
• ✅ Contents section matches actual headings.
• ✅ CC0 license file included.
• ✅ CONTRIBUTING.md with clear submission guidelines.
• ✅ Entry format is correct throughout: - [Name](url) - Description ending with period.
• ✅ ASCII hyphen-dash separator used consistently; descriptions start uppercase.
• ✅ Entries alphabetically sorted within sections.
• ✅ Footnotes section transparently discloses maintainer-authored entries (4 of 62, ~6.5%) — nice touch.

Issues Found

1. No CI workflow. The repository has no .github/workflows/ directory. Most accepted awesome lists run awesome-lint in CI. Running it locally produces an error (Expected a string), suggesting a schema issue in the README that should be investigated.

2. Single squashed commit. The repo was created 2025-11-27 but has exactly 1 commit dated 2026-04-03. The full history appears to have been force-pushed, making organic growth unverifiable. The PR claims "first commit: November 27, 2025" but the git log shows otherwise — this deserves clarification.

3. Uneven curation depth. Web Apps (32 entries) is disproportionately large compared to Windows (1), Linux (1), Cross-Platform (1). Some entries like apps hosted on replit.app or netlify.app random subdomains feel more like weekend projects than curated "awesome" entries. A quality bar beyond "working and publicly available" would strengthen the list.

4. Single contributor. Only the author has contributed. For 62 curated entries, even a few external PRs would demonstrate community interest.

Summary

The description improvement and disclosure additions show good responsiveness. The lint failure, single-commit history, and uneven quality are the main concerns. Adding awesome-lint CI and refining the curation criteria would put this in a stronger position.

[Simply007]

Nice list - I can imagine, the list would be harder to keep up to date.

I have one suggestion I would appreciate from the list - Have some way to mark what AI tool(s) was used for the app to vibecode. This would help me to select the app to explore.