Interactive visuals in conversation

Choose a visual that helps answer the user's question: relationships for an architecture, steps for a process, aligned views for a comparison, or linked inputs and results for a simulation. Every control should visibly change the diagram, selection, result, or explanation. Do not substitute a long statistics report for a relationship diagram or add decorative controls with no effect.

Read the relevant guidance

Read Shared visual guidance through skill_view before creating a visual. Then read the relevant modules, combining them when useful; they describe general capabilities, not a fixed catalog of examples:

• Diagrams: architectures, flows, sequences, relationships and hierarchies.
• Charts: comparisons, trends, distributions, proportions and correlations.
• Data views: dashboards, tables, heatmaps, custom data graphics and maps from available embedded data.
• Interactive explanations: simulations, calculators and controls that visibly change the result.
• Interface mockups: product interfaces and prototypes with local demonstration interactions.
• Information collection: several related choices or constraints needed for an explicitly requested subsequent task.
• Illustrations: explanatory drawings and art.

For example, a selectable architecture uses diagrams plus interactive guidance; a filterable dataset uses charts or data views plus interactive guidance. Choose the visual from the user's question, not from the examples below. A plain answer, Markdown table or static diagram may already be sufficient.