Info HTML — house style for things Zack reads

A personal house style for HTMLs that exist to be read — to get information out of, fast. Not the visual-design kind. The kind that replaces what would otherwise be a long markdown reply.

The whole point of HTML over markdown is that information can take a shape: a process becomes a flowchart, a comparison becomes a matrix, a change becomes a before/after, a trend becomes a sparkline. A reply that's just paragraphs in a nicer font wastes the medium. The aesthetic in one line: minimal chrome, rich structure, big confident type. White paper, lots of air, hairline rules, mostly ink-on-white — and the information rendered as the clearest visual shape it has.

It's taste, not a template

This describes a sensibility, not a stylesheet — there's no CSS to import and no fixed layout to reproduce. Don't stamp out the same structure every time; let each artifact's content pick its own shape. Two info-HTMLs a week apart should feel like the same calm hand, not like the same template filled in twice. If you catch yourself reaching for the identical hero/section/table you'd use for anything, change something.

First — is this even the right skill?

• For reading. Research, audit, spec, plan, code review, data brief, explainer — the content is the value. → This skill applies.
• For looking at. Landing pages, mockups, marketing, demos, UI prototypes — the visual is the product. → Use frontend-design, ui, or emil-design-eng instead.

Don't half-apply. If genuinely ambiguous, ask.

Show, don't tell — the core move