visual-reportlisted

# Visual Report Use this skill to make Japanese HTML artifacts that look good in Chrome and survive conversion to a single-page PDF. The goal is not a proposal template; it is a reusable design direction for creating new HTML or correcting existing HTML. ## Workflow (follow EXACTLY — do not improvise styling) This skill is designed to produce the same quality from any model. Do not synthesize CSS from the prose rules; copy the skeleton and let the checker judge quality. 1. Identify the HTML type: decision-support, research summary, technical verification, or explanation. 2. **New HTML: copy `assets/skeleton.html` verbatim** as your starting file. Replace `{{placeholders}}`, duplicate/remove `<section>` blocks, keep the numbering scheme (`01`, `02`, …) in side TOC, print TOC, and `sec-no` spans. Do NOT rewrite, "improve", or restyle the CSS block — only add component classes already defined there. Existing HTML: edit toward the skeleton's structure and tokens. 3. Read `references/house-style.md` only when you need a rule the skeleton does not answer (component choice, tone, when to drop a section). 4. Keep the HTML self-contained unless the user explicitly asks for linked assets. 5. Preserve the document's real purpose. Do not force every page into a proposal shape. 6. **Diagram triage (MANDATORY): explicitly weigh ALL FIVE families — archify, dataviz, worklog-flow, ragflow, graph-figure — then embed ≥1 when the content is structural.** See `## Diagrams` → *Family triage*.