visual-explainer

Convert terminal outputs into self-contained HTML pages with Mermaid diagrams.

Updated Aug 12, 2018
One-click install
npx skills add https://github.com/ivanov-i/dots --skill visual-explainer-ivanov-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-explainer
Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/visual-explainer
Command: npx skills add https://github.com/ivanov-i/dots --skill visual-explainer-ivanov-i

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts complex terminal outputs into self-contained HTML pages that communicate architecture, diffs, and data in a browser-friendly format.

Core Features & Use Cases

  • Visualizes architecture diagrams using CSS Grid layouts, Mermaid graphs, and HTML tables so teams can review complex systems without chasing ASCII boxes.
  • Generates diff-and-plan visuals (before/after panels, state machines, KPI dashboards) to support design reviews and release planning.
  • Outputs a self-contained HTML document stored locally (e.g., under ~/.agent/diagrams/) that can be opened in a browser for sharing and offline viewing.

Quick Start

Invoke the skill on a terminal output and open the resulting HTML in a browser to view a visual explanation.

Frequently Asked Questions about visual-explainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert complex terminal outputs into shareable HTML diagrams?

You can convert complex terminal outputs into self-contained HTML pages by applying visualization processing that uses Mermaid for graphs and CSS Grid for layout. The generated files are saved locally and opened directly in a browser for sharing and offline viewing.

What is the best way to visualize architecture diagrams from terminal data without using ASCII boxes?

Visualizing architecture diagrams from terminal data is best handled by generating self-contained HTML pages using Mermaid graphs and CSS Grid layouts. This approach renders complex systems as visual HTML artifacts, eliminating the need to chase ASCII boxes during system reviews.

Can I generate visual diff and plan reviews using HTML output?

Yes, you can generate visual diff and plan reviews by converting terminal outputs into HTML pages. The process creates before and after panels, state machines, and KPI dashboards to support design reviews and release planning directly in a browser-friendly format.

Does this HTML visualization approach require external dependencies to render Mermaid diagrams?

No external dependencies are required to render Mermaid diagrams and HTML tables. The pipeline generates a self-contained HTML document stored locally, such as under the ~/.agent/diagrams/ directory, which can be opened in any standard browser without needing additional setup.

How do I use HTML tables and CSS Grid to visualize system data for design reviews?

To visualize system data for design reviews, the pipeline applies CSS Grid for layout and HTML tables for data, rendering terminal outputs as visual HTML artifacts. You invoke the process on a terminal output and open the resulting HTML file in a browser.

Where are generated HTML architecture diagrams stored for offline viewing?

Generated HTML architecture diagrams are stored locally under the ~/.agent/diagrams/ directory. These self-contained HTML documents can be opened in a browser for offline viewing and shared with teams for collaborative system reviews.