Skill

Diagram

gstack

Design

Turns a plain-English description of a flow or architecture into an actual diagram - editable source plus rendered image. It draws explanatory pictures, not user-interface designs: it is reached for to visualize how something works, not to style a screen or critique one.

Situations it fits

Your team needs to map out the steps from 'customer clicks buy' to 'warehouse sends invoice' so non-engineer stakeholders can follow the money trail. You definitely do not want another endless Slack thread with DMs.

Diagram. This skill turns a written process description into a visual map that readers can follow, which is exactly what you need to show how the money moves without building a UI or picking aesthetics.

The support team wrote a coffee-stained paragraph about how tickets jump from bot to agent to supervisor, and the eng lead needs a clean shape to paste into Confluence.

Diagram. The diagram skill takes a verbal walkthrough of a process and renders a schematic image with editable source, designed for visualizing how something works rather than proposing color palettes, critiquing existing screens, or generating UI alternatives. The tempting distractor is design-review-gstack: because the paragraph describes a possibly messy workflow, but the request is explicitly for a forward-looking schematic to paste elsewhere, not an audit of a finished interface.

3 scenarios in the bank answer to Diagram. The rest are in the game.

Skills it gets confused with

These share a family with Diagram, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Diagram does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Diagram is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.