ascii-diagram-renderer

Render ASCII and Unicode box-art diagrams from D2, Graph::Easy, or PlantUML sources.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/SilvrDuck/skills --skill ascii-diagram-renderer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ascii-diagram-renderer
Source: https://github.com/SilvrDuck/skills/tree/main/skills/ascii-diagram-renderer
Command: npx skills add https://github.com/SilvrDuck/skills --skill ascii-diagram-renderer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It prevents messy, misaligned ASCII/box diagrams by generating diagrams from a proper source format (D2, Graph::Easy, or PlantUML) and rendering them before output.

Core Features & Use Cases

  • Diagram-first workflow: creates a small diagram source, renders it, inspects the output, then revises until the geometry is correct.
  • Multi-context activation: supports diagrams in chat, Markdown, docs/specs, PR comments, issue comments, terminal output, architecture notes, and code comments.
  • Multiple renderers: uses D2 for architecture/service flows and Graph::Easy when appropriate, with PlantUML support for sequence diagrams.
  • Label and layout safeguards: enforces short labels, simple structure, and avoids common D2 ASCII backend pitfalls (like $ and multiline labels).

Quick Start

Ask the agent to draw a terminal-friendly ASCII box-and-arrow diagram for the flow you describe, and have it generate the diagram source first, render it, then return the rendered diagram.

Frequently Asked Questions about ascii-diagram-renderer

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

FAQPage Schema
How do I generate clean ASCII architecture diagrams for Markdown documentation?

Rendering ASCII architecture diagrams from D2 or Graph::Easy sources prevents messy misaligned box-art by inspecting the generated geometry first, ensuring accurate communication in Markdown documentation, PR comments, or terminal output.

Can I render PlantUML sequence diagrams as ASCII art in terminal output?

Yes, you can render PlantUML sequence diagrams as ASCII art in terminal output by using PlantUML as the renderer for sequence-like flows, while D2 and Graph::Easy handle architecture and service flow diagrams.

What's the best way to fix misaligned ASCII box diagrams in chat or code comments?

The best way to fix misaligned ASCII box diagrams is using a diagram-first render-and-inspect workflow that generates a proper D2 or Graph::Easy source, renders it, and revises until the box-art geometry is correct.

Does D2 support ASCII backend rendering without breaking multiline labels?

D2 supports ASCII backend rendering for architecture diagrams, but this Skill applies safeguards to avoid common D2 ASCII backend pitfalls like multiline labels and dollar signs to ensure correct geometry.

When should I use Graph::Easy instead of D2 for dependency and interaction maps?

You should use Graph::Easy instead of D2 for dependency and interaction maps when D2 is not appropriate, acting as a fallback renderer while maintaining short labels and simple structure for accurate ASCII output.

Do I need to install external tools to render ASCII diagrams from D2 sources?

No external tools are strictly required to start rendering ASCII diagrams from D2 sources, as the Skill handles generation and inspection internally, though optional renderer toolchains like D2, Graph::Easy, or PlantUML can be used.