html-visualizelisted

## How to use Render interactive HTML the user opens in a browser. Three modes cover the cases — ask, feedback, and visualize. The mode is already determined; do not re-classify it. Pick the active mode from the table below, read its reference doc, and follow it end to end. The user's intent — the questions to ask, the content to mark up, or what to visualize — is the content to render. Carry it into the mode reference's "decide what to render" step. ## Mode routing | Mode | Invoked by | Load and follow | |---|---|---| | `ask` — question/decision form with a blocking submit round-trip | `html-visualize-ask` | [references/ask.md](references/ask.md) | | `feedback` — content (document, plan, or brainstormed options) for inline commenting, with an Apply loop | `html-visualize-feedback` | [references/feedback.md](references/feedback.md) | | `visualize` — non-blocking `--no-wait` serve with always-on footer; user may optionally send a message back | `html-visualize-page` | [references/visualize.md](references/visualize.md) | ## Authoring guidelines — all modes These apply to every mode. The goal is a page the user can take in at a glance and act on without effort. - **Make the page stand alone.** A clear title and a one-line subtitle must orient a reader who has none of the chat context. The user should be able to open, read, and understand the page — or bookmark and share it — on its own. - **Lead with what matters; keep it scannable.** Put the most important content