visual-explanationlisted

# Visual Explanation Turn a relationship-heavy technical explanation into the smallest visual form that makes the relevant structure easier to understand. Keep prose when a sentence or short list is already clearer. ## Selection Card Use this skill for an explicit request to show the current technical topic visually, or when mappings, branching effects, dependent steps, state changes, hierarchy, ownership, layout, or a structural delta are hard to follow in prose. Inputs: the question to clarify, inspected evidence or supplied assertions, the target audience, and the host's rendering capabilities. Do not use it for a simple fact, one-step action, decorative diagram, general data visualization, UI screenshot audit, generated image asset, or codebase architecture recovery. ## Representation-Fit Gate 1. Name the exact comparison, relationship, sequence, state change, hierarchy, or layout the reader must understand. 2. If concise prose is equally clear, stop and use concise prose. 3. Choose one smallest useful form. Add a second view only when it answers a different necessary question. 4. Put the visual next to one short takeaway. Do not repeat the whole visual in prose. ## Form Selector | Need | Prefer | | --- | --- | | Repeated-field mapping or comparison | Table | | Hierarchy, ownership, nesting, component shape, or shallow file responsibility | Tree | | Branching logic or algorithm | Pseudocode | | Caller/callee structure without chronology | Call tree | | R