Every report Claude writes as , it can also build as a small interactive page. The upgrade is always the same sentence:
Turn this into a single self-contained interactive HTML file I can open by double-clicking — no server, no internet, no external libraries.
The phrasing matters, word by word:
- single self-contained file — everything (styles, script, data) inside one
.html, so it travels by email and Teams like any attachment. - open by double-clicking — no dev server, no localhost, no IT involvement. Works on any laptop with a browser, which is every laptop.
- no external libraries — nothing fetched from the internet, so it works offline and there’s no dependency to get blocked by the proxy.
What this unlocks, concretely: a complaints CSV becomes a clickable heatmap with drill-down quotes; a policy diff becomes a side-by-side viewer with changes highlighted; an onboarding checklist becomes a page with checkboxes that remember their state; meeting action items become .ics files that open straight into Outlook.
Add the details you care about as plain sentences — “clicking a row shows the source”, “checkbox state survives closing the page”, “accent colour #007a8a” — and iterate by describing what you see, not by reading code.
And when the page misbehaves visually, remember Claude can look at its own work: “take a screenshot of the page in a headless browser and fix what looks wrong.” You don’t have to be the only QA in the loop.
Every use case in the hub ends with a “level up” step built on this sentence. Learn it once, apply it to anything.