anti-vibecode

사용 방법

설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.

npx skills add https://github.com/melvynx/shared-skills --skill anti-vibecode

시작 전 확인

설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.

원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

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.

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.

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 (npx impeccable install): production

frontend design, from brand to polish.

better: improves one screen

at a time across accessibility, layout, writing, typography and colors, then verifies it.