julia-evaluationlisted

# Julia REPL — Behavioral Rules Use the MCP tools (`eval`, `reset`, `pkg`, `activate`, `session`, `revise`, `log_viewer`, `info`) for interactive Julia work. Prefer `julia script.jl` via bash for one-shot scripts. ## Before Every Eval Always display code in a readable julia code block BEFORE calling eval. The MCP permission prompt shows code as an escaped string which is unreadable. ## After Eval MCP tool results are collapsed in Claude Code. For visual output (plots, heatmaps), tell the user to expand the tool result (Ctrl+O) to see it with full color — do NOT paste ANSI art into your message (it loses colors and streams token-by-token). For structured text (tables, matrices, DataFrames), paste in a fenced code block. Do not paste simple scalars or errors. ## Revise vs Reset Prefer `revise` — it preserves session state. Only `reset` when required. | Change | Action | |--------|--------| | Function/method body or signature | `revise(action="revise")` | | Struct layout (Julia < 1.12) | `reset` required | | Corrupted state / stuck code | `reset` required | After editing `.jl` files, call `revise(action="revise")` to hot-reload (a PostToolUse hook reminds you after `.jl` edits). ## Error Recovery | Error | Fix | |-------|-----| | `UndefVarError` | Re-run definition or check spelling | | `MethodError` | Check argument types | | `LoadError` | `pkg(action="add", packages="...")` | | `cannot redefine` | `reset` (struct layout change) | | Hung/infinite | `eval(code=..., ti