Skill doesn't trigger

Invoke by name and reference 'antivibe style' in prompts

antivibe (Claude Skill) — 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Post-generation explanation pass
Highlights non-obvious choices (error handling, concurrency, memory)
Names alternative approaches explicitly
Flags things the author might not understand
Configurable depth — quick notes vs deep dive

라이브 데모

실제 사용 모습

antivibe-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: antivibe

Learn a new framework while Claude writes in it

👤 Devs picking up an unfamiliar framework (Svelte, Rust, Go) ⏱ ~20 min beginner

언제 쓸까: You'd normally copy Claude's output and hope for the best. Instead, you want to understand.

흐름

Ask for code as usual

Use antivibe. Write a Svelte 5 store for user authentication.✓ 복사됨

→ Code block + teaching pass explaining runes, $state, $derived
Ask for alternatives

What other approaches did you consider? Why this one?✓ 복사됨

→ Named alternatives with tradeoffs
Probe understanding

Quiz me — ask 3 questions about what this code does.✓ 복사됨

→ Actual quiz questions, not a quiz on trivia

결과: Code in your repo you understand and can maintain.

함정

Skipping the explanation pass when in a hurry — Turn the skill off for throwaway spike code, on for anything you'll merge

Have Claude review code you wrote, antivibe-style

👤 Devs who want a critical second look ⏱ ~15 min intermediate

언제 쓸까: You wrote something and want a teacher's eye on it.

흐름

Submit the code

Use antivibe. Here's my implementation [...] — review it like you'd teach it.✓ 복사됨

→ Per-section commentary
Ask what a senior would say

What would a senior engineer on this codebase push back on?✓ 복사됨

→ Specific pushback, not 'add tests'

결과: Concrete improvements with reasoning you internalize.

함정

Claude becomes a hype machine — Prompt explicitly: 'be skeptical; assume the code is wrong until proven'

함께 쓰기: filesystem

Produce teaching-quality explanations for a PR description

👤 Senior devs onboarding juniors through PRs ⏱ ~15 min beginner

언제 쓸까: You want the PR description to double as a teaching doc.

흐름

Feed the diff

Use antivibe. Write a PR description that explains to a mid-level dev why each change is there.✓ 복사됨

→ PR body with rationale per chunk

결과: PR descriptions your team actually reads.

함께 쓰기: github

조합

다른 MCP와 조합해 10배 효율

antivibe-skill + github

Post antivibe-style explanations as inline PR comments

Review this PR with antivibe and leave teaching comments on non-obvious lines.✓ 복사됨

antivibe-skill + filesystem

Walk a junior through a codebase file by file

Use antivibe to explain each file in src/auth/ as if onboarding a new engineer.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
explain_code	code block	Right after generation
list_alternatives	code + goal	Deepening understanding
quiz_me	code block	Testing actual understanding

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Higher than bare generation — the extra explanation pass doubles tokens roughly
금액: Free
팁: Use for signal code only; skip for repetitive boilerplate.

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: Local prompts; code sent to Claude API per normal operation

문제 해결

자주 발생하는 오류와 해결

Explanation is just a restatement of the code

Prompt for alternatives and pitfalls explicitly; Claude sometimes defaults to paraphrase

대안

antivibe 다른 것과 비교

대안	언제 쓰나	단점/장점
Native Claude Code without skill	Ad-hoc teaching requests	Inconsistent; depends on prompt each time
Reading docs + pair programming	Real mastery	Slower; higher quality

antivibe