fused-widgetslisted

# Widgets — getting a rendered result back > **Part of the Fused skill set — don't work from it alone.** Fused is `workspace ⊃ > project ⊃ UDF`. Before acting, also load **`fused-projects`** for the end-to-end > model (creating, running, opening, and deploying a project's widget). For a > question/approval/plan UI load **`fused-feedback`**. See **`fused-guide`** for the > full set — this skill assumes that context. In most Fused flows the thing a human wants back is a **widget** (an interactive dashboard), not a raw value. A widget is a JSON config; running it yields *resolved rows that a renderer turns into a visual*. This skill covers authoring widgets and getting them in front of a human. **There are NO MCP widget tools.** Agents author widget *files*; humans *view* them through the CLI (`fused widget open` / the parley). The separate **flow** UI (`fusedio/flow` — started with the `flow` CLI, or `npx @fusedio/flow` once published) can also render them, but driving flow is **out of scope** for this skill; everything below is the `fused` CLI, never MCP. (See `fused-projects` for where this sits in the project lifecycle, and `fused-cli` for the full `widget` command flag tables.) --- ## What a widget is A widget is a single JSON document — a tree of nodes, each `{ "type": "<component>", "props": { … }, "children": [ … ] }`. It lives in one of two places in a project — **and the two render on different surfaces, so the choice matters:** - **`widgets/<stem>.json`** — a *