HTML Artifact

Create a browser-viewable HTML artifact when complex work needs a richer review surface than a wall of Markdown. Default to one self-contained file; use a split bundle when the planned content is too large for a reviewable single page.

Core rule

Use HTML artifacts for complex, visual, comparison-heavy, reviewable, or shareable outputs. Keep ordinary Markdown for short answers, simple commands, commit messages, tiny summaries, and routine implementation reports unless the user explicitly asks for an artifact.

Output contract

Every artifact must be: