anti-vibecode

---
name: anti-vibecode
description: >-
  Bans the 43 tells of a vibecoded website (purple gradient on black, indigo
  Tailwind buttons, bento grid, liquid glass, sparkles icon, fake counters,
  "Most popular" pricing, the "Create Next App" tab, no legal pages...) while
  Claude builds or reviews a site, so it looks made by a human. Use when
  building, redesigning or reviewing a website, landing page or web app UI,
  or when the user types /anti-vibecode, "vibecodé", "ça fait IA", "looks AI
  generated".
argument-hint: "[audit | fix | rules] [path]"
---

# anti-vibecode

A site generated by an AI agent without direction ends up with the same 43 defaults: the ones every
model reaches for when nobody says otherwise. Visitors spot them in a second and read « made by AI,
nobody cared ». This skill turns each of them into a rule, finds them in the code, and replaces them
with a real choice.

What the user typed after `/anti-vibecode`: `$ARGUMENTS`

## Modes

- `rules` (default when Claude is about to build UI, or no argument): load `references/signs.md` and
  follow it for the rest of the session. Before writing any page, decide the 3 choices that kill most
  tells: one brand color that is not purple or indigo, one typeface that is not Inter / Geist / Space
  Grotesk, and one layout idea that is not a centered hero + 3 feature cards. Say them in one line.
  Answer with « 43 règles actives » (or « 43 rules active ») and the 3 choices.
- `audit [path]`: run the scanner, then check by eye what a regex cannot see. Report only, no edit.
- `fix [path]`: audit, then fix every sign found, highest impact first (the « What is missing »
  section always counts, a site without legal pages is not shippable).

## Audit

1. Run the scanner from this skill's folder on the project root (or the path given):

   ```bash
   node <skill folder>/scripts/scan.mjs <project root>
   ```

   It prints each sign it detected with its number, file and line, and the signs it cannot detect.
   Node 18+, no dependency.
2. Open the site (dev server or the built pages) and check the visual signs the scanner lists as
   « check by eye »: layout, motion, copy, what is missing. Read the landing page copy yourself.
3. Report as a checklist: `✓ NN  <sign>` when clean, `✗ NN  <sign>  <file:line>  → <fix>` when found.
   End with the count: `NN/43 signes trouvés`.

## Fix

- Follow the « Instead » column of `references/signs.md` for each sign found. Never swap one cliché
  for another (purple gradient → blue gradient is still the same sign).
- The project's own brand wins: if a brand book, `DESIGN.md`, `PRODUCT.md` or design tokens exist,
  take colors and type from them.
- Real content over filler: no invented testimonial, user count or logo wall. When the real thing does
  not exist yet, remove the block, never fake it. Ask the user for the real numbers.
- Missing legal pages: create `mentions-legales` and `confidentialite` (or `legal` and `privacy`)
  pages with the fields the user must fill marked `TODO`, never invented company details.
- Run the scanner again at the end and show the before / after count.

## Going further

For a full design pass after the cleanup, two skills pair well with this one:

- [Impeccable](https://github.com/pbakaus/impeccable) (`npx impeccable install`): production
  frontend design, from brand to polish.
- [better](https://github.com/Melvynx/shared-skills/tree/main/skills/better): improves one screen
  at a time across accessibility, layout, writing, typography and colors, then verifies it.