Learning Commands · Reference & Visualization

/diagram command

Interactive diagram visualization of a topic

2 min read

Interactive diagram visualization of a topic

At a glance

Field Value
Command /diagram
Usage `/diagram [--topic=] [--scope=free
Category reference
Execution server
Context pok
Response type mini-canvas
Active PoK required yes

Parameters

  • topic (optional) — Topic to visualize as a diagram

Examples

/diagram
/diagram --topic=HTTP Request Lifecycle
/diagram --scope=unit
/diagram --type=flowchart
/diagram --scope=free --topic=OSI Model --type=architecture

How it works

The diagram command creates an interactive diagram visualization of your learning content.

Diagram types:

  • Flowchart: Decision flows with yes/no branches, start/end nodes, and process steps
  • Architecture: Layered system diagrams with grouped components and inter-layer connections
  • Process Flow: Linear step-by-step process chains with sequential connectors
  • Comparison: Side-by-side column layouts comparing concepts, with optional cross-links
  • Venn Diagram: Overlapping circle sets showing shared and unique properties
  • Hierarchy: Top-down tree structures showing parent-child relationships
  • Workflow: Action/work flow diagrams with feedback loops, retry cycles, and decision branches

How it works:

  1. The AI generates a structured diagram with nodes, edges, and optional groups
  2. Each node has a label, description, and a check question
  3. Click nodes to explore their descriptions and answer check questions
  4. Correct answers mark nodes as completed (green checkmark)
  5. Complete all nodes to see your results

Options:

  • topic: Specific topic to visualize (optional — uses current topic if not specified)
  • scope: Content scope — pok (current topic), unit (entire unit), all (all units), free (any topic)
  • type: Diagram type (optional — AI chooses the best type if not specified)

Tips:

  • Use --type=flowchart for decision processes and algorithms
  • Use --type=architecture for system designs and layered structures
  • Use --type=comparison to contrast two or more concepts side by side
  • Use --type=workflow for work processes with feedback loops and retry cycles

Was this article helpful?