jmunch-claude-code-setup CLAUDE.md

jmunch-claude-code-setup

Core value: Enforcement and tracking layer that ensures Claude Code uses jCodeMunch/jDocMunch MCP servers for code/doc navigation, saving 85-95% of tokens

Active Context

Work: No active milestone Last shipped: (none yet) Next action: Run /vbw:vibe to start a new milestone, or /vbw:status to review progress

VBW Rules

• Always use VBW commands for project work. Do not manually edit files in .vbw-planning/.
• Commit format: {type}({scope}): {description} — types: feat, fix, test, refactor, perf, docs, style, chore.
• One commit per task. Each task in a plan gets exactly one atomic commit.
• CHANGELOG rule: Every entry in CHANGELOG.md must have a short human-readable explanation — what it does, what it fixes, or what it adds. Never list raw commit messages alone.
• Never commit secrets. Do not stage .env, .pem, .key, credentials, or token files.
• Plan before building. Use /vbw:vibe for all lifecycle actions. Plans are the source of truth.
• Do not fabricate content. Only use what the user explicitly states in project-defining flows.
• Do not bump version or push until asked. Never run scripts/bump-version.sh or git push unless the user explicitly requests it, except when .vbw-planning/config.json intentionally sets auto_push to always or after_phase.

Code Intelligence

Prefer LSP over Search/Grep/Glob/Read for semantic code navigation — it's faster, precise, and avoids reading entire files:

• goToDefinition / goToImplementation to jump to source
• findReferences to see all usages across the codebase
• workspaceSymbol to find where something is defined
• documentSymbol to list all symbols in a file
• hover for type info without reading the file
• incomingCalls / outgoingCalls for call hierarchy

Before renaming or changing a function signature, use findReferences to find all call sites first.

Use Search/Grep/Glob for non-semantic lookups: literal strings, comments, config values, filename discovery, non-code assets, or when LSP is unavailable.