visual-explain

# Visual Explain Explain concepts visually using ASCII diagrams, tables, flow charts, and structural maps. The visual IS the explanation — prose is secondary. ## When to invoke Trigger phrases: "explain visually", "show me a diagram", "draw this out", "chart this", "map this", "visualize this", "show me how this works", "diagram this", "sketch this out". Also invoke when `/visual-explain` is used directly. ## Visual vocabulary Use the right format for the right job: | Concept type | Visual format | |---|---| | Flows and pipelines | ASCII arrow diagrams (`→`, `↓`, `──▶`) | | Architecture / components | Box diagrams with labeled connections | | Comparisons and trade-offs | Tables with columns per option | | Hierarchies and containment | Tree structures or nested box diagrams | | Temporal sequences | ASCII sequence diagrams (actor columns + arrows) | | State changes | Before/after side-by-side diagrams | | Decision logic | Flowcharts with diamond decision nodes | ## Rules 1. **Lead with the visual.** Always produce the diagram or table FIRST. Prose comes after, if needed at all. 2. **Minimal prose.** Keep explanatory text to 1-2 sentences per diagram. The visual carries the explanation — prose only clarifies what the visual cannot. 3. **Prefer multiple small diagrams over one complex one.** Break a system into 2-3 focused visuals rather than cramming everything into a single diagram. Each diagram should have one clear point. 4. **Consistent visual language:** - `[...