# HTML Rendering This is a format-rendering reference — it describes how to render any artifact in HTML, independent of which skill is producing it. It is paired with a section contract (`plan-sections.md`, `brainstorm-sections.md`, etc.) that describes *what* the artifact contains. This reference describes *how* HTML specifically presents it. The same content rendered by different skills shares the same HTML principles. The HTML artifact is the *only* artifact the skill produces for that run — output mode is exclusive (markdown OR HTML, never both). Report-only `spec-doc-review` and human readers consume HTML directly. `spec-work` is a consumer only when the producer's section contract identifies the artifact as an implementation-ready software plan; it is not a consumer of requirements-only brainstorm or ideation HTML. The agent-consumability rules below make those artifact-kind-specific reads work. HTML review does not grant document mutation authority: `spec-doc-review` resolves `mutation_policy: report-only` with `mutation_reason: html-artifact`, keeps `fixes_applied: 0`, and returns findings or producer-fix candidates without invoking Markdown mutation paths. ## Hard invariants These hold regardless of which skill produced the artifact. - **Single self-contained HTML5 file.** No companion `.css`, `.js`, or `.svg` files. CSS lives in `