Curation guidelines

• Apps, tools, games, content sites, dev tooling, hardware projects, weird experiments.
• A meaningful slice of code or design was made in collaboration with an AI assistant — and you can name which one(s).
• It works. There's a live URL someone can visit, even if it's a demo or a free tier.
• It's yours — built by you or a team you were on, not a tutorial copy or wrapper around someone else's product.
• You can write one sentence about what you learned doing it. Even a small one.

• Pure AI wrappers ("I prompted GPT to summarise X") with no product layer of their own.
• Lead-magnets, link farms, SEO doorway pages, crypto pump sites, scam templates.
• Anything illegal, sexual content involving real or generated minors, doxxing tools, malware, copyright laundering.
• "Coming soon" landing pages with no working product.
• Submissions with fake builder names, fake LLM lists, or invented LOC/build-time numbers we can spot-check and disprove.
• Resubmissions of a project that was already rejected, unless something material changed.

• Generative AI projects are welcome — but lean toward novel uses, not "yet another chat UI on top of Claude".
• No-code / low-code builds count if there was real configuration, prompt engineering, or design judgment involved.
• Forks of public templates count if you added a meaningful product layer; not if you swapped the logo.
• NSFW adult-content projects are evaluated case by case — well-built consenting-adult tools may be accepted with a content tag; exploitative content is rejected outright.
• Closed-source is fine. We don't require a public repo.

1. Title and tagline that actually describe the thing — no marketing fluff.
2. Honest stack and LLM lists. We can usually tell if "GPT-4o, Cursor, Claude Opus 4.7, Aider, Cline, v0, Bolt, Lovable, Cursor Composer" is real or padding.
3. One specific tip in the builder's-tip field. "Be brave" is not a tip. "Have the assistant write the failing test first" is.
4. If you have a repo, link it. We'll show the GitHub stars and last-commit on the project page.
5. A real screenshot or thumbnail. AI-generated cover art is allowed but rarely helps.

Real-person review usually within 3 days. We'll email you on approve or reject. Rejections include a one-line reason so you can fix and resubmit.

Disagree with a rejection? Email admin@vibcod.dev or use the contact form. We'll re-review. We've changed our mind plenty of times.