HTML Artifacts

Generate a visual document that earns its use of HTML: the result should be easier to look at, compare, or manipulate than prose alone. Default to a self-contained local .html document, not a website, dashboard, or slide deck.

Non-Negotiables

• Ground first. Read the source material and trace the relevant behavior before designing the artifact.
• Default to document mode. The artifact must stand on its own for an asynchronous reader. Use presentation mode only when explicitly requested or clearly intended for a live talk.
• Keep the static story complete. Interaction may deepen the explanation; it must not be required to discover the main conclusion.
• Make interaction answer a question. Every control must satisfy: reader question → action → immediate visible answer. Remove controls that do not.
• Produce one true offline file by default. Inline CSS, JavaScript, SVG, data, and essential assets. Do not rely on CDNs, remote fonts, fetch, or a server.
• Keep it local unless asked. Artifacts may expose source code, architecture, or review findings. Do not publish, upload, or create a public URL without explicit permission.
• Validate the final file in a browser. Do not call an artifact finished from source inspection alone.

Choose the Mode