swt-labs

swt-labs/vibe-better-with-claude-code-vbw

Approve the VBW contract (requirements, checks, plans) and the project commands it may run. Only the user can run this.

Compress a long instruction file (CLAUDE.md, rules, docs for Claude) into terse caveman style to save tokens, keeping every fact, ...

Show or change VBW settings - the model profile (quality, balanced, budget), per-role models, how much VBW does on its own, and th...

Bring a VBW 1 project (.vbw-planning/) into VBW 2 through a short Q&A; the old folder stays unless you choose to delete it.

Investigate a bug from three angles at once (reproduce, trace the code, recent changes) and get its root cause with evidence and a...

Think something through with VBW before building (a decision, an idea, a concern): plain questions, trade-offs, a recommendation, ...

Check that everything VBW needs is in place (tools, Claude Code version, workflows, status line, the project) and fix what is wron...

Make a quick fix or small change without planning ceremony; VBW's guards stay on and every proof is re-run afterwards so nothing p...

What VBW does and every VBW command, with when to use each.

Set up VBW in this git repository (.vbw/ with the spec and the plan of record) and the VBW status line, then start agreeing on wha...

Ask the user, once at the start of a project, how much software they have built, how VBW should explain things, how involved they ...

List the ideas parked for later, with what you can do with each.

Let VBW work through named backlog items on its own, within a spend ceiling. Only the user can run this.

Map an existing codebase (stack and commands, structure, conventions, tests, risks) so VBW plans fit the code; saves .vbw/map.md.

Check whether the VBW panel and its sound work on this Claude Code.

Stop for now safely - VBW checks nothing is left half-done and notes where you are, so /vbw:resume picks up exactly there.

Switch how VBW works in one go - which AI models it uses, how much it does on its own (Careful, Standard, Fast, or your own mix), ...

Check the finished work now - run every proof and explain in plain words what passes, what fails and what only you can judge.

Prepare a bug report or idea about VBW as a GitHub issue; you see the full text and decide before anything is sent.

Research a question on the web, in documentation and in this project, and get a sourced answer with a recommendation (up to four S...

Pick up where you left off - where the project stands, what was decided, and the next step.

Set up, check or remove RTK, a third-party tool that compresses command output to save tokens; uses RTK's own official installer.

Look for the best tools for this project (safety scanners, code-quality tools, test frameworks, community skills), show a short so...

Where this VBW project stands - progress, the roadmap and the next step. Reads only.

Offer the user at most three yes-or-no suggestions when requirements are proposed or a plan is presented for approval. Used by the...

Teach Claude and VBW's agents this project's conventions (naming, structure, testing, style); saved as Claude Code rules in .claud...

Keep an idea for later in the VBW backlog, or list the backlog.

Sort every new idea the user brings as now, next or later, with a reason and a size, before any requirement, planning or file chan...

Remove VBW from Claude Code - the status line setting first, then the plugin; project files stay.