Claude artifact report

Put the session's work on one page the user can read, keep and share: everything found and everything suggested, answered against the request that started the session. The report is the deliverable; chat carries only its link and a short summary.

$ARGUMENTS, when given, narrows the focus or names the audience. Otherwise the report covers the whole session and is written for the user.

Words used below:

• Request: what the user asked for in this session. With several requests, the report answers each.
• Item: one finding (something discovered, measured or decided) or one suggestion (a change worth making, tied to the findings behind it).
• Evidence: what makes an item checkable: a file and line, a command and its output, a measured value, a source link, a screenshot.
• Cold reader: someone who missed the session. Write for them: every term defined, every piece of context restated on the page.
• Visual: a chart, diagram, table, screenshot or illustration. A visual earns its place when it shows what prose could only describe.
• Pick: an item the reader ticks to act on. Picks feed the page's Copy prompt, which the user pastes back to you.

1. Inventory

Go back through the whole session (messages, files read and changed, commands and their output, research, subagent reports) and list every item with its evidence. Re-check items the session may have overtaken (a bug since fixed, a number since re-measured) against the current files, and record the current state.