antivibe MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

antivibe-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "antivibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mohi-devhub/antivibe",
        "~/.claude/skills/antivibe"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "antivibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mohi-devhub/antivibe",
        "~/.claude/skills/antivibe"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "antivibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mohi-devhub/antivibe",
        "~/.claude/skills/antivibe"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "antivibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mohi-devhub/antivibe",
        "~/.claude/skills/antivibe"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "antivibe-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mohi-devhub/antivibe",
        "~/.claude/skills/antivibe"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "antivibe-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/mohi-devhub/antivibe",
          "~/.claude/skills/antivibe"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add antivibe-skill -- git clone https://github.com/mohi-devhub/antivibe ~/.claude/skills/antivibe

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: antivibe

Learn a new framework while Claude writes in it

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

Wann einsetzen: You'd normally copy Claude's output and hope for the best. Instead, you want to understand.

Voraussetzungen

Skill installed — git clone https://github.com/mohi-devhub/antivibe ~/.claude/skills/antivibe

Ablauf

Ask for code as usual

Use antivibe. Write a Svelte 5 store for user authentication.✓ Kopiert

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

What other approaches did you consider? Why this one?✓ Kopiert

→ Named alternatives with tradeoffs
Probe understanding

Quiz me — ask 3 questions about what this code does.✓ Kopiert

→ Actual quiz questions, not a quiz on trivia

Ergebnis: Code in your repo you understand and can maintain.

Fallstricke

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

Wann einsetzen: You wrote something and want a teacher's eye on it.

Ablauf

Submit the code

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

→ Per-section commentary
Ask what a senior would say

What would a senior engineer on this codebase push back on?✓ Kopiert

→ Specific pushback, not 'add tests'

Ergebnis: Concrete improvements with reasoning you internalize.

Fallstricke

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

Kombinieren mit: filesystem

Produce teaching-quality explanations for a PR description

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

Wann einsetzen: You want the PR description to double as a teaching doc.

Ablauf

Feed the diff

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

→ PR body with rationale per chunk

Ergebnis: PR descriptions your team actually reads.

Kombinieren mit: github

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

antivibe-skill + github

Post antivibe-style explanations as inline PR comments

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

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
explain_code	code block	Right after generation
list_alternatives	code + goal	Deepening understanding
quiz_me	code block	Testing actual understanding

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: Higher than bare generation — the extra explanation pass doubles tokens roughly
Kosten in €: Free
Tipp: Use for signal code only; skip for repetitive boilerplate.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None

Datenabfluss: Local prompts; code sent to Claude API per normal operation

Fehlerbehebung

Häufige Fehler und Lösungen

Explanation is just a restatement of the code

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

Skill doesn't trigger

Invoke by name and reference 'antivibe style' in prompts

Prüfen: ls ~/.claude/skills/antivibe/SKILL.md

Alternativen

antivibe vs. andere

Alternative	Wann stattdessen	Kompromiss
Native Claude Code without skill	Ad-hoc teaching requests	Inconsistent; depends on prompt each time
Reading docs + pair programming	Real mastery	Slower; higher quality

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen