Ask HN: How can you tell a site/app is vibe coded?
1–10 of 13 posts
Re: Ask HN: How can you tell a site/app is vibe coded?
#2Re: Ask HN: How can you tell a site/app is vibe coded?
#3Re: Ask HN: How can you tell a site/app is vibe coded?
#4I honestly don't mind it. For these B2B SaaS apps its nice to have some site consistency. It almost reminds me of a a new "Bootstrap" way of doing things.
Re: Ask HN: How can you tell a site/app is vibe coded?
#5Re: Ask HN: How can you tell a site/app is vibe coded?
#6Re: Ask HN: How can you tell a site/app is vibe coded?
#7If you can't tell, does it matter?
Re: Ask HN: How can you tell a site/app is vibe coded?
#8Re: Ask HN: How can you tell a site/app is vibe coded?
#9Re: Ask HN: How can you tell a site/app is vibe coded?
#101. Impeccable (github.com/pbakaus/impeccable) — a CLI that scans HTML/CSS/JSX for 59 deterministic anti-pattern rules. It catches the actual visual tells: zero-offset dark glows on text, 1px borders paired with 40px shadow blur, Inter/Roboto/Geist as the default "tasteful" font.... etc.. I wont list all 59 here.
2.Taste Skill (github.com/Leonxlnx/taste-skill) — preventive rather than detective. It's a set of SKILL.md files you load into your coding agent (Cursor, Claude Code, etc.) before generation so the slop never gets created in the first place.
---
everyone knows about Em-dash overuse, but there are other tells like the dark background offset glow, thick boarders, flat display style, over use of techy color schemes like navy blue (especially with gradients) and emojis in headers as large style iconography. there are like 5 common fonts ai's use etc.. the key is, your llm is going to reason that these are all good safe choices and even when you tell them to be different they will give you great sounding logic as to why to use them... which is exactly the problem. every llm 'reasons' themselves into using the same choices so the sites all look the same.