html-diagram
HTML Diagram
Review the SVG diagrams used throughout references/html-effectiveness/.
There are a bunch in there, and some of them are focused on architecture and whatnot.
After reviewing them, create an HTML file that is strictly for visualizing the architecture and understanding the stack.
It should not be prose-heavy. It should simplify more into a full-screen diagram and whatnot.
Build a high-quality diagram in SVG. Take your time iterating on the diagram more than anything.
If it makes sense, make the diagram interactive and able to visualize and animate different sequences of system behavior.
Also review references/architecture-example.html — a finished example of this skill done well (full-screen SVG stage, clickable nodes, flow chips that light up and animate request paths).
Always include dark mode: hand-rolled CSS variables on :root / html.dark, a small theme toggle button, localStorage persistence, and an apply-before-paint script in <head> (default to prefers-color-scheme). Style the SVG through CSS classes using those variables — never hard-coded hex inside the SVG — so the diagram follows the theme.
Always make floating overlays dismissible. Any card or panel that overlays the SVG stage (e.g., a detail panel, a legend, a side card) MUST have a visible close button, and MUST re-open when the user clicks a relevant node or filter. This prevents floating panels from permanently blocking content on the full-screen stage.