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.
A situation 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.
3 scenarios in the bank answer to diagram (gstack). The rest are in the game.
Skills it gets confused with
These share a family with diagram (gstack), which is another way of saying they are the ones you might reach for by mistake.
- design-consultation (gstack)Studies your product and the design landscape around it, then proposes a whole design system from scratch — aesthetic direction, typography, color, spacing, motion. It is the propose-a-fresh-system step, not a critique of what you already have and not a way to explore several throwaway variations.
- design-review (gstack)Looks at an interface you have already built with a designer's eye and calls out — then fixes — the specific flaws: inconsistent spacing, weak hierarchy, generic AI-slop styling, sluggish interactions. It critiques and repairs existing work, rather than proposing a new system or generating alternatives to choose between.
- design-shotgun (gstack)Generates several distinct design variations of the same thing at once and lays them on a comparison board so you can react to real options and iterate. Its job is breadth — many candidates to choose among — not proposing one considered system or auditing a design you have settled on.
Knowing what diagram (gstack) does is the easy half. Telling it apart from the others under time pressure is the game.
Today's sessiondiagram (gstack) is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.