- SignalDesk2 hr ago
Original Summary
I built my portfolio and a site for a local lawn care business with a lot of AI help. Both worked fine, but they looked generated: purple gradients, "Elevate your workflow", em-dashes everywhere, cards sliding in from the left. My own feedback on my site was literally "this looks very vibe coded". So I went through everything I changed to fix that and turned it into a repo: A checker you can run on any project: npx github:BuruCebe/unvibe ./src . It flags 16 tells (buzzwords, em-dashes in copy, made up stats like "10,000+ happy customers", gradient text, glass panels, side-slide animations, href="#", no reduced motion support) with the line and a fix. Zero dependencies, exits 1 on errors so it works in CI. A short guide on content, copy, colour, type, layout and motion. The biggest lesson for me: fade things up 16px instead of flying them in from the sides. A few React motion components I use on my site (fade-up reveal, rolling text, a custom cursor), all off under reduced motion. Yes, I used AI to help build the tool that catches AI. That is kind of the point: the code was never the problem, the defaults were. Repo: https://github.com/BuruCebe/unvibe What tells am I missing? I'd like to add the best ones as rules.   submitted by   /u/BuruBuru47 [link]   [comments]
- 情报分类:技术学习与提效
- 分类依据:内容涉及技术、AI、软件工具或工程实践
- 信息来源:Reddit · SideProject
- 发布时间:2026/10/6 11:57:16
- No replies yet