visualize-it
Skill4 starsChanged 17 days agoMITView on GitHub
Explain a concept, feature, problem, flow, or piece of code as a visual HTML page — diagrams, charts, tables, interactive or animated sections. Claude artifact when available, otherwise a standalone HTML file.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-firstSkill
- claude-project-rulesSkill
- compact-markdownSkill
- humanizeSkill
- pr-reviewSkill
- empty-commitSkill
- github-issue-creatorSkill
- git-mergeSkill
- git-worktreeSkill
- handoff-sessionSkill
- html-landing-pageSkill
- offload-taskSkill
- readme-craftSkill
- skill-auditSkill
- study-notesSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
No argument → the topic currently under discussion (last response, code just read, problem being debugged).
- Distinctive: line 20
Read the real source first: code, docs, logs, the reply being explained.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Visualize It
Turn something hard to grasp from code, docs, or a chat reply into one visual page that makes it click.
Subject
- Argument given → visualize that.
- No argument → the topic currently under discussion (last response, code just read, problem being debugged).
- Subject unclear → ask before building.
Ground it
Read the real source first: code, docs, logs, the reply being explained. Names, numbers, steps, and order on the page come from the source — a wrong picture teaches the wrong model, and looks convincing. Something inferred, not verified → label it on the page.
Design
Format, layout, and content are your call per subject. Pick whatever explains it most simply: diagrams, flowcharts, sequence/state views, tables, charts, step-through or animated walkthroughs, interactive controls, side-by-side comparisons, worked examples. One clear idea beats many decorations; skip any section that adds no understanding.
Output
- Artifact tool available (Claude) → publish as a Claude artifact, following its design/skill guidance.
- Otherwise (Codex, VS Code, other harness) → write one self-contained file
./visualize-<slug>.htmlin the current working directory. Opens by double-click: no build step, no local server, CSS/JS inline. File already exists → ask before overwriting.
Done
Reply with the artifact link or file path, plus one line on what the page shows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.