show-me

Pick the smallest view that makes the point, set it beside one or two lines of text, stop. One view per question; two if a second genuinely adds an axis. Never all of them.

Pick the view

Render target decides the format

• Use trees, pseudocode, or diffs in plain terminals. Use Mermaid when the actual destination renders it.
• Use an interactive visualization or self-contained HTML when interaction or spatial layout adds value. Follow the host's output-directory convention and return a link. Open the file only when requested, using the available platform mechanism; do not assume macOS or a graphical session.

Examples

Call tree — runtime order:

submitForm
  createSession
    persistPrompt
    launchAgent
  navigateToSession

Component tree — structure, state, and the module a component comes from:

<SessionPage> (apps/example/src/routes/session.tsx)
  useSessionEvents()
  <SessionToolbar>
    <RunSkillButton> (packages/ui)

File tree — responsibility, one line each:

src/
├── commands/       # parses user actions
├── sessions/       # owns session state
└── transport/      # sends API requests

Diff — when the surrounding shape already exists. Diff whichever view fits the topic; any of the above takes diff markers. Here, pseudocode:

 on(save)
-  write content
+  if content is unchanged
+    return cached result
+  write new content
+  invalidate cache

Rules

• Include only the calls, files, props, states, and boundaries this question needs. Elide the rest with …. Do not pad a view toward completeness.
• Real paths, real names, real data. A tidy diagram with invented labels is worse than prose.
• Show the whole block instead of a diff when most of it is new, when the omitted context hides ownership or order, or when the user needs something copyable.
• Skip the preamble. The visual is the answer; the prose is a caption.