---
name: visualize
description: Create a native interactive calculator, conditional form, chart or data table when local input changes help answer the user. Also handles repairs to an existing Kelivo interface.
---

# Interactive answers

1. Choose a small native interface when the user benefits from changing inputs,
   comparing values or exploring supplied data. Use prose for a single fact or
   explanation without useful interaction. State a useful conclusion outside
   the interface, and cite real data or label synthetic values as example data.
2. Read `references/protocol.md`. Read `references/content.md` for layout and
   text; `references/inputs.md` for controls, validation and actions;
   `references/data.md` for charts/tables; `references/functions.md` when computing.
   Read `references/examples.md` for three complete, validated patterns.
3. Emit one top-level `kelivo-ui` fence using the advertised header, complete
   single-line declarations and an explicit root. Keep all requested controls
   reachable from root and derive results from their bindings. Styling belongs
   to the app's theme; select only catalog semantics.
4. Check unique names, allowed properties, required fields, units, mappings and
   every referenced ID before closing the fence. Test the reasoning for changed
   inputs, not just initial values. Hidden fields retain values but do not block
   form validation. Ask creates an editable draft; it never sends automatically.

For repairs, preserve the user's intended behavior and correct the supplied
bounded diagnostics/source. Return a complete corrected interface with a short
explanation. The repair draft is ordinary editable chat text, not a tool call.

Only when supported native components cannot express a self-contained interaction,
read `references/web.md`. Use native charts, calculators, forms and tables whenever
possible. Copy/read-aloud behavior is described in `references/semantics.md`.