show-me

Files (7)

• SKILL.md
• openai.yaml · agents/
• calldiff.md · references/
• html.md · references/
• pr-description-template.md · references/
• visual-forms.md · references/
• visual-pr.md · references/

SKILL.md (first lines)

# Show me

Explain the current topic visually. Skip the preamble. Pick the smallest view that makes the key point clear.

## Pull requests

Whenever creating a PR or updating its description, follow [`references/visual-pr.md`](references/visual-pr.md). This branch applies to every PR, including backend, documentation, and configuration changes; it does not authorize creating or publishing a PR without a user request.

## Choose the form

Read the active host's note in [hosts](../yesh-router/references/hosts/) for its rendering limits, such as terminal width in [pi](../yesh-router/references/hosts/pi.md). Where the host renders HTML inline in the chat, such as [T3 Code](../yesh-router/references/hosts/t3.md), lean into it: flows and DAGs, call trees, and `calldiff` output go to [viz](../viz/SKILL.md), and other comparisons take the HTML branch. Pseudocode, diffs, and copyable code stay as text. Elsewhere, choose from this list as written.

- Use pseudocode for logic or an algorithm.
- Use a call tree for runtime control flow that is only nested calls; once it branches, retries, or exits on failure, it is a flow for viz.
- Use a component tree for UI structure and state ownership.
- Use a file tree for responsibility or a broad refactor.
- Use a sequence for multi-component interaction or data flow: viz `view: seq` where HTML renders, a numbered markdown list elsewhere. A data model is a viz graph of entities and their links. Never use Mermaid.
- Use a diff when the surrounding shape exists and the point is what changes.
- Use a whole code block when omitted context would hide ownership or order, or the user needs a copyable target.
- Use `calldiff` for a changed call tree or stack.
- Use [viz](../viz/SKILL.md) for a flow or DAG with branches or failure paths, a call tree or call diff too long to read as text, or whenever the user wants to click through it. Elsewhere it opens a temp HTML page.
- Use focused HTML for a visual comparison or concept too dense for viz.

Never draw boxes or arrows (`┌ │ ─ ▶ →`, `-->`) in a code block; they read as noise in T3 Code, GitHub, and narrow terminals. A drawing that needs them is a viz.

Load [`references/visual-forms.md`](references/visual-forms.md) only when drawing a text form (tree, diff, pseudocode, numbered sequence, transition table). Load [`references/calldiff.md`](references/calldiff.md) for call-tree commands. Load [`references/html.md`](references/html.md) only for the HTML branch. For viz, read and follow its skill.

## Present

Place each visual beside the short text it supports. Keep only the calls, files, props, states, and boundaries needed for the current question. Use several forms only when each adds distinct information.

## Completion

The explanation is complete when the selected visual answers the named question, every shown path or relationship is grounded in available evidence, the artifact or command output is accessible to the user, and any unverified or unavailable part is stated.

From Yeshwanthyk/agent-skills, MIT.

More from Yeshwanthyk/agent-skills