showlisted

# Show Answer at a glance: What connects to what? What changed? What proves it? Build an evidence view, not a decorative diagram; source, diff, and command output remain ground truth. ## 1. Set the focus Use the request and repository context. Do not ask for details that can be discovered from the repository. State the smallest boundary that answers the question. Gather only: - definitions, callers, consumers, configuration, and ownership; - current diff or before/after revisions; - verify command, exit code, decisive output, and coverage gaps. Never expose private chain-of-thought. Show observable evidence and conclusions. ## 2. Normalize the evidence Keep five kinds: **Entities**, **Relations**, **Changes**, **Proof**, and **Gaps**. Label inference as `? inferred`; never draw a guessed edge as fact. ## 3. Choose the smallest useful view Prefer the first form that carries the relationship clearly: - decision → compact pseudocode; - runtime calls → call tree; - ownership → shallow tree; - 3+ interacting parts → Mermaid flow/sequence; - structural change → before/after diff; - completion → requirement-to-proof map; - clear prose → one sentence or short list. Use one primary view. Add another only for a different question. Reserve focused HTML for dense UI or interactive state. Keep HTML temporary unless the user asks to keep it, and open it only with permission. ## 4. Render with a stable grammar ```text A --> B calls or moves data A --owns--> B