---
name: show-me
description: Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts. Use when the user asks to "show me", wants a diagram, a call tree, a component tree, a file tree, a data-flow sketch, or a before/after shape of a change.
---

Help the user understand the current topic of conversation visually. Skip the preamble and keep prose brief. Pick the smallest view that makes the key point clear.

- Show logic or an algorithm as pseudocode:

```text
on(save)
  if content is unchanged
    return cached result
  write new content
  return fresh result
```

- Show runtime control flow as a call tree:

```text
submitForm
  createSession
    persistPrompt
    launchAgent
  navigateToSession
```

- Show UI structure as a component tree, including state and module boundaries that matter:

```tsx
<SessionPage> (apps/example/src/routes/session.tsx)
  useSessionEvents()
  <SessionToolbar>
    <RunSkillButton> (packages/ui)
```

- Show file responsibility or a broad refactor as a shallow file tree:

```text
src/
├── commands/       # parses user actions
├── sessions/       # owns session state
└── transport/      # sends API requests
```

- Show component interaction, control flow, or data flow with Mermaid:

```mermaid
sequenceDiagram
    participant User
    participant UI
    participant Daemon
    User->>UI: choose command
    UI->>Daemon: send expanded prompt
    Daemon-->>UI: stream result
```

- Show numbers (a trend, a distribution, a comparison, a breakdown) as an interactive chart: a ```vega-lite fence holding a Vega-Lite spec with inline `data.values`. Omit `width` so it fills the column; keep the data aggregated. When `opensession-charts` is available, pass the spec to `make_chart` first: it reports compile errors instead of leaving a silent code block and offloads large data into a session asset.

```vega-lite
{
  "title": "Runs per day",
  "mark": "bar",
  "data": {"values": [{"day": "Mon", "runs": 12}, {"day": "Tue", "runs": 9}]},
  "encoding": {
    "x": {"field": "day", "type": "nominal", "sort": null},
    "y": {"field": "runs", "type": "quantitative"}
  }
}
```

- Show a screenshot, recording or rendered file where the reader needs it, not at the end: an `OPENSESSION_IMAGE: /abs/path.png` or `OPENSESSION_VIDEO: /abs/path.mp4` line renders in place at the column's width. A short plain line directly under it is its caption. For a before/after, `OPENSESSION_COMPARE: /abs/before.png /abs/after.png` renders one slider.

- Other blocks the transcript renders live (each stays readable as plain text elsewhere):
  - `> [!NOTE]`, `[!TIP]`, `[!IMPORTANT]`, `[!WARNING]`, `[!CAUTION]` on a quote's first line: a callout.
  - `$$` on its own lines or a ```math fence: typeset math; `$x^2$` inline with the delimiters touching the expression.
  - ```csv, ```tsv or ```table (header row first): a sortable, filterable grid with copy as CSV. Use it for more than a handful of rows; a markdown table is fine for a few.
  - ```json (large): a collapsible tree with a raw toggle. ```ansi or ```terminal: terminal output with its colours.
  - ```palette (one colour per line, optional name): swatches that copy on click; a hex in a codespan gets a chip.
  - ```metrics (`Label: value (delta)` per line): a row of metric cards.
  - ```choices (one reply per line): chips the reader clicks to send that reply. Use it when you end a turn with a small set of options.
  - ```tree (indented, trailing `/` for directories, or `tree` CLI output): a collapsible file tree.
  - ```artifact (a complete HTML document or fragment) or ```svg: a sandboxed preview with a source toggle, scripts never run. ```slides (markdown split on `---`): a swipeable deck.

- Use `diff` when the point is what changes and the surrounding shape already exists. Match the diff shape to the topic.

For a component change:

```diff
 <SessionPage>
   useSessionEvents()
   <SessionToolbar>
+    <RunSkillButton />
   <SessionTimeline>
+    <SkillResultCard />
```

For a file-layout change:

```diff
 src/
 ├── commands/
+│   └── show-me.ts       # expands the slash command
 ├── sessions/
-└── transport.ts
+└── transport/
+    ├── client.ts
+    └── stream.ts
```

For a call-tree or call-stack change:

```diff
 submitForm
   createSession
     persistPrompt
+    expandSkillMention
     launchAgent
-  navigateToSession
+  navigateToSession
+    subscribeToEvents
```

For a state or control-flow change:

```diff
 on(save)
-  write content
+  if content is unchanged
+    return cached result
+  write new content
+  invalidate cache
```

- Show the whole block when most of it is new, when omitted context would hide ownership or order, or when the user needs a copyable target shape:

```ts
function expandSkill(command: string): string {
  const skillName = command.slice(1);
  return `use the ${skillName} skill`;
}
```

- For a visual UI, layout, state comparison, or concept too dense for Mermaid, write one focused HTML file: a diagram, an infographic, or a short slide deck, whichever fits the point. Match the product's colors, type, spacing, and components; use real labels and data; support desktop and mobile. Save it as a session asset so it previews live in the Assets tab:

```text
opensession-assets.write_asset
  path: show-me-{description}.html
  content: <the page>
  description: one line on what it shows
```

Then name the asset path in your reply (`show-me-{description}.html`) so the reader gets a direct open link. Keep it self-contained, or write companion files as extra assets; relative references resolve in the preview. Do not `open` it or screenshot it: sessions run headless, and the asset is the live version.

### guidance

Place each visual next to the short text it supports. Keep only the calls, files, props, states, and boundaries needed to answer the user's current question or the options to resolve the current discussion point.

You may use one of these, you may use several, it is unlikely you will use all of them. Use your judgement and don't overwhelm the user.

Adapted from [humanlayer/skills](https://github.com/humanlayer/skills/blob/main/plugins/show-me/skills/show-me/SKILL.md).