Explain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Explain concepts visually using ASCII diagrams, tables, flow charts, and structural maps. The visual IS the explanation — prose is secondary.
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.
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 |
Lead with the visual. Always produce the diagram or table FIRST. Prose comes after, if needed at all.
Minimal prose. Keep explanatory text to 1-2 sentences per diagram. The visual carries the explanation — prose only clarifies what the visual cannot.
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.
Consistent visual language:
[ boxes ] for components, modules, services──▶ or → for data flow and control flow─── for connections and relationships< diamonds > for decisions( rounded ) for inputs/outputs│ and ─ for structure linesSystem explanations follow this order:
Comparisons follow this order:
Keep diagrams under 40 lines tall and 72 characters wide. If a diagram exceeds this, split it into multiple diagrams with clear labels.
[ User Request ]
│
▼
[ Auth Middleware ] ──▶ [ 401 Unauthorized ]
│
▼
[ Route Handler ]
│
┌────┴────┐
▼ ▼
[ Cache ] [ Database ]
│ │
└────┬────┘
▼
[ Response ]
Option A Option B Option C
──────────────────────────────────────────────────────────
Speed Fast Medium Slow
Cost $$$ $$ $
Complexity High Medium Low
Reliability High High Medium
──────────────────────────────────────────────────────────
✓ Recommended: Option B — best balance of cost and speed.
Client Server Database
│ │ │
│── POST /api ──▶│ │
│ │── INSERT ─────▶│
│ │◀── OK ─────────│
│◀── 201 ────────│ │
│ │ │
egregore/
├── bin/ Shell scripts (Runtime, notifications, telemetry)
├── skills/ Cognitive skill definitions
│ ├── harvest/
│ └── tui-design/
├── memory/ Symlink → shared memory repo
│ ├── people/
│ ├── handoffs/
│ └── knowledge/
└── .claude/
├── commands/ Slash command definitions
└── skills/ Claude Code skill files
BEFORE AFTER
┌──────────────────┐ ┌──────────────────┐
│ Monolith │ │ API Gateway │
│ ┌────────────┐ │ │ │
│ │ Auth │ │ └─────────┬─────────┘
│ │ API │ │ │
│ │ DB │ │ ┌───────┼───────┐
│ │ Queue │ │ ▼ ▼ ▼
│ └────────────┘ │ [ Auth ] [ API ] [ Worker ]
└──────────────────┘ │ │ │
└───┬───┘ │
▼ ▼
[ DB ] [ Queue ]
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
The English summary is being prepared. Showing the original description.
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
The English summary is being prepared. Showing the original description.
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
The English summary is being prepared. Showing the original description.
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
The English summary is being prepared. Showing the original description.
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
The English summary is being prepared. Showing the original description.
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
The English summary is being prepared. Showing the original description.