← ClaudeAtlas

whatislisted

What Is This — explain anything as a picture-first HTML page. Use when the user types /whatis <topic>, or asks what something is / how it works and would be better served by big diagrams than by paragraphs.
suyuan2022/suyuan-skill · ★ 568 · AI & Automation · score 86
Install: claude install-skill suyuan2022/suyuan-skill
# whatis Explain like I'm someone who knows nothing about this topic, using an HTML page with big pictures and few words. No Artifact tool in this environment: write a self-contained HTML file (inline SVG/CSS, no external deps) to a temp directory (e.g. `$TMPDIR` or `/tmp`), then `open` it. If the current context is not enough to explain the topic, gather enough context yourself before drawing. Every node in a diagram must be backed by evidence; never fabricate. Draw real diagrams in SVG, freely picking and combining whatever fits: flowchart, sequence diagram, state diagram, architecture/block diagram, C4, dependency graph, call graph, ER diagram, class diagram, DFD, swimlane, deployment diagram, timeline, Gantt, git graph, before/after comparison, bar/line chart, treemap, heatmap... If none fits, design your own — expression comes before templates. Tables are for enumerations only and don't count as diagrams. A diagram exists to make structure visible: who talks to whom, what causes what, what changes when. Draw each one in the shape the reader's eye already knows — boxes for parts, arrows for actions, lanes for actors, time flowing one way. Make each diagram read at two distances: at a glance only the backbone shows — a name per box, a verb per arrow, one path the eye can follow; the detail lives in a quieter layer of smaller, dimmer annotations that never competes with the backbone. Color like a print magazine: warm paper background, ink for text and lines, one muted