Explain the current topic or a proposed design visually with types and signatures, pseudocode, a call tree, a component tree, a file tree, a diff, a whole block, a Mermaid diagram, or a published Artifact.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add bendrucker/claude --skill show-me --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Show Me?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bendrucker-show-me)More formats (shields.io, HTML) on the badges page.
---
name: show-me
description: Explain the current topic or a proposed design visually with types and signatures, pseudocode, a call tree, a component tree, a file tree, a diff, a whole block, a Mermaid diagram, or a published Artifact.
argument-hint: "[<what to show>]"
disable-model-invocation: true
---
# Show Me
Explain $ARGUMENTS visually. Pick the smallest view that makes the point, and keep the prose around it short.
## Arguments
With no argument, show the current topic of conversation.
## Formats
Pick one format or several, rarely all.
### Types and Signatures
The shape of code before an implementation exists, showing the interface and the seam:
```ts fragment
interface Skill {
name: string
body: string
}
interface SkillSource {
read(name: string): Promise<Skill>
}
function expand(command: string, source: SkillSource): Promise<string>
```
### Pseudocode
Logic or an algorithm:
```text
on(save)
if content is unchanged
return cached result
write new content
return fresh result
```
### Call Tree
Runtime control flow inside one process:
```text
submitForm
createSession
persistPrompt
launchAgent
navigateToSession
```
### Component Tree
UI structure:
```tsx fragment
<SessionPage> (apps/example/src/routes/session.tsx)
useSessionEvents()
<SessionToolbar> (packages/ui)
<SessionTimeline>
```
### File Tree
File responsibility or the shape of a refactor:
```text
src/
├── commands/ # parses user actions
├── sessions/ # owns session state
└── transport.ts # sends API requests
```
### Diff
A change against a shape that already exists:
Component tree:
```diff
<SessionPage>
useSessionEvents()
<SessionToolbar>
+ <RunSkillButton />
<SessionTimeline>
+ <SkillResultCard />
```
File tree:
```diff
src/
├── commands/
+│ └── show-me.ts # expands the slash command
├── sessions/
-└── transport.ts
+└── transport/
+ ├── client.ts
+ └── stream.ts
```
Call tree:
```diff
submitForm
createSession
persistPrompt
+ expandSkillMention
launchAgent
navigateToSession
+ subscribeToEvents
```
State and control flow:
```diff
on(save)
- write content
- return result
+ if content is unchanged
+ return cached result
+ write new content
+ return fresh result
```
### Whole Block
Most of the block is new, omitted context would hide ownership or order, or the user needs a copyable target shape:
```ts
function expandSkill(command: string): string {
const skillName = command.slice(1)
return `use the ${skillName} skill`
}
```
### Mermaid
Interaction that crosses modules or processes, and data flow through them:
```mermaid
sequenceDiagram
participant User
participant UI
participant Daemon
User->>UI: choose command
UI->>Daemon: send expanded prompt
Daemon-->>UI: stream result
```
### Artifact
A rendered UI, a layout, a state comparison, or a concept too dense for Mermaid. Publish it as an Artifact.
## Planning
When the topic is work not yet done, show the proposed shape rather than describing it. Types and signatures carry a design first, then the call tree, then the file layout. Where the work changes something that exists, show the proposal as a diff.
## Scope
Place each visual next to the short text it supports.
Keep only the calls, files, props, states, and seams that answer the question on the table.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!