vbw:teach

VBW Teach $ARGUMENTS

Context

Working directory:

!`pwd`

Plugin root: ${CLAUDE_PLUGIN_ROOT} Conventions:

!`cat .vbw-planning/conventions.json 2>/dev/null || echo "No conventions found"`

Codebase map:

!`ls .vbw-planning/codebase/INDEX.md 2>/dev/null && echo "EXISTS" || echo "NONE"`

Guard

If no .vbw-planning/ dir: STOP "Run /vbw:init first." (check .vbw-planning/config.json)

Convention Structure

Stored in .vbw-planning/conventions.json:

{
  "conventions": [{
    "id": "CONV-001", "rule": "API routes go in src/routes/{resource}.ts",
    "source": "auto-detected", "category": "file-structure",
    "confidence": "high", "detected_from": "PATTERNS.md", "added": "2026-02-10"
  }]
}

Sources: auto-detected (from codebase map) | user-defined (manual via /vbw:teach) Categories: file-structure | naming | testing | style | tooling | patterns | other Confidence (auto-detected only): high (80%+) | medium (50-80%) | low (<50%)

Behavior

No arguments: Display known conventions

1. Read .vbw-planning/conventions.json. If missing, show empty state with examples (/vbw:teach refresh and /vbw:teach "convention text").
2. Display conventions grouped by category. Tag: [auto . {confidence}] or [user]. Show totals.
3. AskUserQuestion: "What would you like to do?" Options: "Add a convention" | "Refresh from codebase" (if map exists) | "Done"

Text argument: Add a convention

A1. Parse: Extract rule text. Infer category:

• File paths/dirs → file-structure
• Casing/naming/prefixes → naming
• Test/coverage/vitest/jest/pytest → testing
• Style/formatting/imports → style
• Tool names (eslint, prettier, pnpm) → tooling
• Patterns/architecture/state/API → patterns
• Otherwise → other

A2. Conflict check: Compare against ALL existing conventions:

• Semantic conflict (contradicting rules): display ⚠, AskUserQuestion: "Replace existing" | "Keep both" | "Cancel"
• Redundancy (essentially same rule): display ○, AskUserQuestion: "Replace with new version" | "Add as separate" | "Cancel"