canvaslisted

# Canvas A canvas presents an analytical artifact in the user's browser. Technical documents use the bundled React reader with Markdown as the content source; free-form design artifacts use standalone HTML. ## 1. Decide whether to use a canvas The trigger is **user intent**, not response shape. Ask: would the user benefit from viewing this output as its own standalone artifact, separate from the chat? Use a canvas for analyses, audits, reviews, reports, dashboards, and tables past a handful of rows. Skip it when the output is a means to an end — a drafted message, a code fix, a deliverable in another tool — or when the user is working inside an existing artifact or doing targeted debugging. ## 2. Route to a presentation type Two kinds of canvas, one reference file each. Read exactly the one you route to: it carries the scaffold, the patterns, and the visual rules for that branch. | Branch | The canvas is | Read | | --- | --- | --- | | **Technical** | documentation of engineering work — audit, architecture review, code health report, benchmark, migration plan, progress dashboard. The content carries everything; the visual only has to stay out of the way. | [technical.md](technical.md) — React Markdown reader with the accepted dark layout | | **Design** | an artifact whose layout carries meaning — editorial report, visual comparison, anything the user asked to look a certain way. | [design.md](design.md) — compose freely inside the anti-slop rules | Route to **technical*