diagram-generator
Diagram generator
Add a diagram only where a cold reader would otherwise assemble a mechanism in their head from the prose — a flow that branches or joins, an exchange between parties, a lifecycle, a topology — and draw it so that the shape alone still says something. The diagram content is English; the report to the user is in the user's language.
The contract lives in the project
This skill carries craft, not format. The allowed diagram types, the accessible-text fields, the sections a diagram may stand in, how many an item holds, the size a rendered diagram must fit, what a fence may not contain and the validation commands all come from the project's diagram contract, which AGENTS.md / CLAUDE.md names, together with the glossary that defines its words. Read both in full before any operation. Where this skill and the contract meet, the contract wins. A project with no contract gets a report saying so, and no files.
Resolve the task
| Choice | Values |
|---|---|
| Operation | create, improve, audit — read it off the request |
| Destination | one lesson — a Bite, or the authored page of a Lab — named by the request |
| Scope | that lesson's body, in full; a Checkpoint or a Mock exam is never a destination |
| Policy | what the brief says about this batch — which sections to prefer, how dense, which types to balance; absent a brief, draw what passes the gates |
The knowledge boundary is always the lesson itself: every node, edge, state, participant and label is something the lesson's prose states, in the lesson's own words. Primary sources verify correctness and add nothing to the boundary. Ask the user one question only when the destination is ambiguous in a way that changes which file is touched; everything else has a default above. Sameness across a batch — every lesson closing with the same flowchart of its scenario — is the brief's to prevent and the reviewer's to catch, because one run sees one lesson; pnpm diagram:check --inventory lists what the corpus already holds.