fused-feedbacklisted

# Fused feedback — ask the human through a visual UI > **⛔ STOP — load companion skills before your first tool call.** Fused is > `workspace ⊃ project ⊃ UDF`. If the task touches a **project, UDF, or data-bound > widget** (anything with `{{ref}}`/`sql` — e.g. opening an existing project's > widget), you MUST load **`fused-projects`** (end-to-end model + how > projects/widgets are addressed) and **`fused-widgets`** (component catalog + > `{{ref}}` resolution) **before running any command or editing any file**. Do not > reverse-engineer project paths or widget props ad hoc — that context is in those > skills (e.g. the exact `sql-table` prop set). Only a pure static ask (a plain > `widget open` with no project/`{{ref}}`) is safe to do from this skill alone. See > **`fused-guide`** for the full set. Instead of asking the human a question as terminal text, render a **real browser UI** and get a **structured answer back as JSON**. You author a small JSON-UI config (a tree of `{type, props, children}` nodes — text, inputs, buttons), open it with `fused widget open`, and the command **blocks until the human responds**, then prints their answer on stdout. This is Fused's local feedback loop repackaged for **Claude Code**: a visual-planning surface for questions, approvals, and plan reviews, in the user's own workspace. > **CLI vs in-app.** This skill is the **CLI** `widget open`/parley surface — you > author a static widget and read the human's submitted `action`/`params`. The > s