Skill

Same Page

Re-explain your reasoning with evidence and visuals so users truly understand.

Use in Claude Code
/amplify:same-page

Same Page helps users understand your reasoning by re-explaining previous messages in a clear, structured format. It dynamically designs the explanation shape based on the prior message—using evidence blocks, comparison tables, flow diagrams, or other layouts—and always includes at least one ASCII visualization. Each claim is backed by concrete evidence with a confidence rating (High/Medium/Low), ensuring transparency and trust.

Key Insights

Dynamic Explanation Design

The explanation format adapts to the prior message: narrative arcs for single decisions, comparison tables for trade-offs, flow diagrams for processes, and more. No rigid templates.

Evidence with Confidence

Every claim is supported by specific evidence (file, line, URL, command output) and rated High/Medium/Low with a basis. Low-confidence claims are explicitly flagged.

ASCII Visualizations

At least one ASCII diagram per explanation, chosen dynamically: flow diagrams for processes, trees for hierarchies, tables for comparisons, etc. Compact and terminal-friendly.

Re-verify, Don't Recall

Re-reads source files and re-runs commands to ensure accuracy, rather than relying on memory of earlier tool calls. Honest and up-to-date.

How It Works

1

Identify Key Claims

Extract key claims from the last substantive message.

Look at the most recent substantive message, extract decisions, facts, and recommendations. Group claims into 2-5 themes if the message is long.

2

Design Explanation Format

Choose a layout that fits the prior message.

Select from narrative arcs, per-claim sections, comparison tables, flow diagrams, confidence overviews, or timelines. State the format choice briefly.

3

Gather Evidence & Rate Confidence

Support each claim with concrete evidence and a confidence level.

For each claim, cite specific artifacts (file, line, URL, command output). Rate confidence High/Medium/Low with a one-line basis. Re-read files and re-run commands as needed.

4

Create ASCII Visualization

Design at least one ASCII diagram to clarify structure.

Choose a visual style (flow, tree, stack, table, graph) that matches the content. Keep diagrams under ~20 lines and ~72 columns. Add a one-line caption.

5

Close with Synthesis

End with a summary, caveats, or next steps.

Provide a short synthesis, checklist of caveats, or 'what to verify next'. Explicitly call out low-confidence areas and open questions.