yava-code

Vibe Wise MCP — Design skill for Claude Code

Design community

Universal MCP server port of VibeWise: design-first gate for any coding agent (Claude Code, Cursor, Codex, Antigravity).

How to install Vibe Wise MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open yava-code/vibe-wise-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Vibe Wise MCP does

Universal MCP server port of VibeWise: design-first gate for any coding agent (Claude Code, Cursor, Codex, Antigravity). Ask the user's approach, record decisions in .vibe-wise/, write code only after approval.

Alternatives in Design

  • Deepen — Spare-budget design pass 1.1k ★
  • Design Plugin — A Claude Code plugin that helps you make confident UI design decisions through rapid iteration 674 ★
  • Home Assistant Vibecode Agent — Home Assistant MCP server agent 617 ★

README

VibeWise MCP

Universal [MCP](https://modelcontextprotocol.io) port of [VibeWise](https://github.com/nykooi1/vibe-wise), a Claude Code plugin that puts learning and design first.

One gate for **every** MCP-capable coding agent: Claude Code, Cursor, Codex CLI, Antigravity, and others:

  • The agent asks your approach before building; you shape the design.
  • Your decisions and the project map are recorded locally in .vibe-wise/.
  • Code is written only after you approve an implementation checkpoint (vibe_confirm).
  • No account, backend, or telemetry. Notes are local Markdown.

How the gate works

you describe the task
        │
        ▼
Build checkpoint ── agent asks how YOU would approach it ── your reasoning recorded
        │
        ▼
Design checkpoint ── proposal + tradeoffs ── "Confirm and continue" records it (no code)
        │
        ▼
Implementation checkpoint ── exact code changes ── "Implement this step" authorizes code
        │
        ▼
agent writes code, runs checks, gives an Implementation report

The three checkpoints are not mandatory stops; when the design is already clear the Implementation checkpoint confirms it too. The pending decision lives in `.vibe-wise/progress.md`, survives restarts and compaction, and is the ledger the tools read and write: restarting a session is never approval.

Tools

Tool Purpose
vibe_status Check the gate: active, stage, pending decision, what to do next
vibe_start Activate learning mode; create .vibe-wise/; onboard or resume
vibe_onboard_answer Record one onboarding answer; get the next question
vibe_checkpoint Open build / design / implement checkpoint
vibe_confirm Record the user's decision: confirm / discuss / approach
vibe_report Record the implementation report after approved coding
vibe_map_update Update the evidence-based project map
vibe_pause Pause / resume the gate ("Learning mode: pause