diagram-first

Draw ASCII diagrams to explain code, systems, and data flows.

102|4|Updated Apr 15, 2009
One-click install
npx skills add https://github.com/mikker/dotfiles --skill diagram-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagram-first
Source: https://github.com/mikker/dotfiles/tree/main/agents.symlink/skills/diagram-first
Command: npx skills add https://github.com/mikker/dotfiles --skill diagram-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagram-first explanations using ASCII visualizations (sequence diagrams, flowcharts, component maps) to explain code, systems, request/response flows, pipelines, concurrency, and comparisons. Use when the user asks to "draw an ASCII diagram", "show the flow/logic", "visualize the architecture", "explain how it works", or when a diagram would reduce ambiguity in a technical explanation.

Core Features & Use Cases

  • Answer questions with a short ASCII diagram first, then a concise explanation.
  • Prefer visual structure over prose when describing flows, architecture, or logic.
  • Diagram types include Sequence, Flowchart, Component map, Pipeline diagrams, State machines, and Side-by-side comparisons.

Quick Start

Provide an ASCII diagram first to illustrate the requested concept, then follow with a concise explanation.

Frequently Asked Questions about diagram-first

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

FAQPage Schema
How do I visualize system architecture using ASCII diagrams?

You can visualize system architecture by drawing ASCII component maps and flowcharts directly in text. This approach presents the visual structure upfront to reduce ambiguity when explaining code, distributed systems, and data flows.

What is the best way to draw a sequence diagram for an API request flow?

Drawing an ASCII sequence diagram is a concise way to visualize API request and response interactions. It maps sequential or parallel component communications upfront, followed by a brief textual explanation of the logic.

Can I use ASCII flowcharts to explain code logic and pipelines?

Yes, ASCII flowcharts can explain code logic and pipelines by mapping out state machines and data transformations visually. Presenting the diagram first provides immediate clarity on the flow before detailing the concise textual breakdown.

When should I use ASCII diagrams instead of prose for technical explanations?

Use ASCII diagrams instead of prose when explaining flows, architectures, or logic where visual structure reduces ambiguity. Diagrams are ideal for side-by-side comparisons and illustrating concurrency across distributed components.

How to create a component map for a distributed system?

Create a component map for a distributed system by drawing an ASCII diagram that illustrates the relationships and interactions between parallel or distributed components. Follow the visual map with a concise explanation of the system architecture.