VibeWise is a Claude Code plugin that makes the AI explain the design before it writes anything

A junior engineer asking Claude Code to build a feature usually gets working code and no idea why that code is the right shape.

VibeWise is a Claude Code plugin, published by GitHub user nykooi1 on September 29 and sitting at 300 stars four days later, that reverses the order. The plugin asks the developer for an approach before writing anything, walks through the trade-offs, and only then writes the code. After the code lands, Claude explains what it changed and why. The repository is MIT-licensed and the project README names three audiences: aspiring engineers, junior developers, and experienced engineers working in an unfamiliar stack.

What a session looks like

The example in the README is a Notion-style notes app with notes that can live in several folders. The exchange is a design conversation first: when the user says a note can belong to multiple folders and that deleting a folder should delete its notes, VibeWise responds with "Trip ideas is in both Travel and Summer. Deleting it removes it from both. When someone deletes Travel, what should happen to that note in Summer?" The user picks a rule ("keep it in Summer"), and only then does the plugin let Claude write.

The plugin runs on Claude Code with Python 3 as its only dependency and no extra Python packages. It is approved for Anthropic's Claude directory, according to the README, but not listed in the public community marketplace yet, so for now it installs from the author's own GitHub marketplace inside Claude Code. Anyone who wants to use it should read the project README for the exact commands, which Anthropic will likely replace with a single click once the directory listing goes live.

The audience that owns this problem

VibeWise does not block Claude from writing; it inserts a design checkpoint before each step. The author's own framing is that an experienced engineer approaching a new repository benefits from the same checkpoint as a junior approaching their first one. Claude builds a system map of an existing codebase before suggesting work on it.

Juniors who skip the planning step are the obvious audience. Less obvious: the senior engineer being asked to work in a stack they have not used in three years, who would normally spend an hour reading before touching anything, and now has an interactive map of the codebase instead. The traction on this plugin, 300 stars in four days, suggests the shape fits a real complaint about agent-written code. Teams building juniors into AI-assisted workflows have a specific use for a tool that forces the design conversation before the AI reaches the keyboard. Measured against the output of a plain prompt, the slower start is the point.

Source

• nykooi1/vibe-wise on GitHub