Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/swt-labs/vibe-better-with-claude-code-vbw/llms.txt

Use this file to discover all available pages before exploring further.

Supporting commands handle everything that doesn’t fit the main build loop: one-off fixes, backlog management, session continuity, project conventions, and installation health.

​
Discussion and planning

​
/vbw:discuss [phase]

Run the discussion engine standalone, outside of /vbw:vibe. 
/vbw:discuss [phase-number]
Same engine as /vbw:vibe --discuss. Auto-calibrates between Builder mode (fast, pragmatic) and Architect mode (thorough, exploratory) based on conversation signals. Generates phase-specific gray areas, explores them conversationally, and captures decisions to {phase}-CONTEXT.md. Use this when you want to explore a phase’s design space before committing to a plan — without triggering the full vibe loop.

​
Quick execution

​
/vbw:fix

Apply a quick, obvious fix in Turbo mode. 
/vbw:fix
One commit, no ceremony. Use this when the fix is clear and you don’t need the full agent pipeline to add a missing comma or correct a typo.

​
/vbw:debug <bug description>

Investigate a bug using systematic root cause analysis. 
/vbw:debug "description of the bug or error"
Routes to the Debugger agent, which follows a hypothesis → evidence → root cause → fix protocol. At Thorough effort with ambiguous bugs (intermittent, multiple possible causes, no clear error), VBW spawns 3 parallel Debugger teammates — each investigating a competing hypothesis independently. The strongest evidence wins; contributing factors are noted.

​
Backlog

​
/vbw:todo

Add an item to the persistent backlog. 
/vbw:todo
Backlog items survive across sessions. Use this for “we should really…” thoughts that would otherwise die in a terminal tab.

​
/vbw:list-todos

Browse and act on pending backlog items. 
/vbw:list-todos
Shows all pending todos with computed ages and priority. Lets you pick one and route it directly to /vbw:fix, /vbw:debug, /vbw:vibe, or /vbw:research.

​
Session management

​
/vbw:pause

Save a session note for the next time you pick up this project. 
/vbw:pause
State auto-persists in .vbw-planning/ — /vbw:pause just lets you leave a sticky note for future you.

​
/vbw:resume

Restore full project context from .vbw-planning/. 
/vbw:resume
Reads STATE.md, ROADMAP.md, phase plans, and phase summaries to reconstruct where you left off.
You don’t need to run /vbw:pause before /vbw:resume. VBW’s state lives in .vbw-planning/ at all times — resume works from any session, including after a /clear or a machine restart.
Don’t use /clear to “reset” a conversation mid-project. It discards in-memory context that VBW needs for the current session. Use /vbw:pause to capture a note, then start a new session and run /vbw:resume to restore context from the ground truth in .vbw-planning/.

​
Skills and configuration

​
/vbw:skills

Browse and install community skills from skills.sh. 
/vbw:skills [--search <query>]
Detects your project’s tech stack, suggests relevant skills, and installs them with one command. Use --search <query> to search the full skills.sh registry (~2,000 community skills).

​
/vbw:config <key> <value>

View and modify VBW settings. 
/vbw:config [key value]
Run without arguments for an interactive settings table. Settings you can configure:
SettingDescription
effortEffort profile: thorough, balanced, fast, turbo
autonomyAgent autonomy: cautious, standard, confident, pure-vibe
plain_summaryPlain-language summaries after each phase
skill_suggestionsSuggest relevant skills during init and plan
auto_install_skillsAuto-install recommended skills without prompting
VBW detects when your live settings have drifted from your active profile and offers to save the changes as a new profile.

​
/vbw:profile [name]

Switch between work profiles or create a custom one. 
/vbw:profile [profile-name]
Profiles change effort, autonomy, and verification tier in a single command. See the profiles reference for the full table of built-in presets.

​
Conventions and teaching

​
/vbw:teach

View, add, or manage project conventions. 
/vbw:teach
During /vbw:init, VBW auto-detects conventions from your codebase (naming patterns, testing approach, architecture decisions). You can add new conventions manually at any time. VBW warns about conflicts before adding and injects all conventions into agent context via CLAUDE.md — QA verifies them as part of every phase check.

​
Health and help

​
/vbw:doctor

Run 16 health checks on your VBW installation. 
/vbw:doctor
/vbw:doctor --cleanup
Checks:
  1. jq installed
  2. VERSION file present
  3. Version sync with marketplace.json
  4. Plugin cache present and valid
  5. hooks.json valid JSON
  6. Agent YAML files present (expects 7)
  7. config.json valid JSON
  8. Script permissions correct (executable)
  9. gh CLI available
  10. sort -V support 11–14. Runtime health: stale teams, orphaned processes, dangling PIDs, stale markers
  11. Watchdog status (tmux only)
  12. CLAUDE.md sections up to date
--cleanup resolves runtime findings and refreshes VBW-owned CLAUDE.md sections. Use this first when something feels broken.

​
/vbw:help

Display the command reference. 
/vbw:help

Build docs developers (and LLMs) love

Get started for freeTalk to us