Show Me

by humanlayerca7c8088db69No license5.1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

AI-generated overview

Turns the current conversation topic into concise visual explanations: pseudocode, trees, diffs, Mermaid diagrams, or a focused HTML artifact.

What it does
This skill instructs the agent to explain the topic under discussion visually instead of in long prose. It selects the smallest suitable view: pseudocode for logic, call trees for control flow, component trees for UI structure, file trees for code layout, Mermaid for interaction or data flow, and diffs for changes. When a topic is too dense for those, it produces a single focused HTML file such as a diagram, infographic, or short slide deck, styled to match the product, and opens it for the user.
When to use it
Use it when a conversational topic is easier to grasp as a picture than as text, such as explaining an algorithm, a refactor, a component change, or a data flow. It suits moments when the user needs a compact, copyable shape or a visual comparison rather than a written explanation.
Requirements
No scripts or packages are required; it is instructions only. Producing the optional HTML artifact assumes the agent can write a local HTML file and open it in a browser.

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
  • 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. Then open it for the user:
Bash(open path/to/show-me-{description}.html)

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.

Source and attribution

Source:humanlayer/skillsinplugins/show-me/skills/show-meat commitca7c808

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal