Skip to content

hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-diagram

hyper-diagram

Verified

Use this skill when the user asks to draw, diagram, visualize, or map any structure - architecture, flowchart, data flow, sequence, state machine, ERD, class model, tree, mind map, timeline, schedule, or layered stack - as a polished standalone HTML plus a JPG by default, and a one-page vector PDF on request. Write a typed JSON spec, render it with automatic layout, and verify overlap, overflow, and page checks before delivery. Do not use for numeric data charts, UI mockups, illustrations, or slide decks.

rules/diagram-selection.md

View on GitHub
# Diagram Selection

Use this rule file before deciding what to draw. It owns the structure-to-type choice, the split rule, and the content and wording rules every spec follows.

## 1. Structure → Type

Ask what the reader must answer, then pick the first row that fits.

| The reader asks | Structure | Type |
|---|---|---|
| What parts exist and how do they connect? | components, services, boundaries | `architecture` |
| What happens next, and where does it branch? | steps, decisions, loops | `flowchart` |
| Where does the data go and what changes it? | sources, transforms, sinks | `dataflow` |
| Who calls whom, in what order? | participants, ordered messages | `sequence` |
| What status can it be in, and what moves it? | states, transitions | `state` |
| What tables exist and how do they relate? | entities, keys, cardinality | `erd` |
| What types exist and how do they depend? | classes, interfaces, members | `class` |
| What contains what, with one parent each? | strict hierarchy | `tree` |
| What ideas hang off one topic? | radial brainstorm | `mindmap` |
| When did things happen? | ordered dated events | `timeline` |
| How long does each task take and what waits on what? | dated tasks, dependencies | `gantt` |
| Which layer sits on which? | stacked tiers with members | `layers` |

Tie-breaks:

- A request that names a type uses it, unless the structure cannot be drawn in it; then say so and use the fitting type.
- A process with decisions is `flowchart`; a process that is mostly one service calling another is `sequence`.
- Containment with cross-links is `architecture` with groups, not `tree`.
- Mermaid input keeps its meaning, not its styling: `flowchart`/`graph` → `flowchart` (or `architecture` for a component map), `sequenceDiagram` → `sequence`, `stateDiagram` → `state`, `erDiagram` → `erd`, `classDiagram` → `class`, `gantt` → `gantt`, `mindmap` → `mindmap`, `timeline` → `timeline`.

## 2. Size And Split

- Aim for 5-25 elements. Above about 40 nodes, or 9 sequence participants, draw an overview plus one detail diagram per area, each a separate spec and file set.
- One diagram answers one question. A second question becomes a second diagram.
- Leave out elements that do not change the answer. Fold repeated instances into one node with a count in `sub` ("워커 ×4").

## 3. Content Rules

- `title`: the subject and the view, as a noun phrase ("결제 서비스 아키텍처"). Never "다이어그램" alone.
- `subtitle`: the scope and the as-of point ("범위: 주문 생성부터 정산까지 · 기준 2026-11-08").
- `label`: the name the team uses, short; product and code names as written. `sub`: one role, tech, or port detail.
- Edge `label`: a verb or a protocol that says what crosses ("토큰 검증", "SQL", "정산 이벤트"). Avoid "사용", "연결", "호출" alone. Leave an edge unlabeled only when its meaning is obvious from the two ends.
- `kind` carries meaning, not taste: use the kind that matches what the node is, so the legend reads true. Use `primary` edges for the one main path; `async`, `auth`, `data`, `error`, `return`, `deploy` only when that is what the edge is.
- `description`: two to four sentences that walk the main path in words and name every inferred element ("인증 서버의 위치는 설정 파일에 없어 추정했습니다").
- Korean wording follows the user's language rules: plain declaratives, no filler.

## 4. Evidence

- From a repository, read the files that prove each element (entry points, config, compose, schema, routes) before drawing it.
- An element with no proof is drawn only when the picture would mislead without it, and it is named as inferred in `description`.

## Sources

> Checked 2026-11-08.

| Claim | Source |
|---|---|
| Title, legend, specific relation labels, element type made explicit | <https://c4model.com/diagrams/notation> |
| Mermaid diagram families used as input mapping | <https://mermaid.js.org/intro/> |
| Long description beside a complex image | <https://www.w3.org/WAI/tutorials/images/complex/> |
| The type table, the size bounds, and the split rule | this package's choice |

### Evidence grade

`LOCAL` - the selection table and size bounds are this package's design, not a validated optimum.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall