HTML Communication

When to Use

Use this skill for any request to produce a readable HTML artifact for a human — whether it is called a plan, a spec, a write-up, findings, a summary, a report, a comparison, or a set of UI mocks. The word "plan" is often absent. What the requests share is: a document to read outside the terminal, and a link to open it.

Do not use it for HTML that is part of the product being built (app templates, components, marketing pages). This skill is for documents about work, not shipped UI.

Writing the HTML

Settle the brief first

Before writing any markup, know:

• Audience and job — who reads this, and what should they understand or decide by the end?
• Form — a linear document, a comparison, a report with a recommendation, or something presentation-like?
• Register — most of what this skill produces is workmanlike: quiet hierarchy, exact spacing, restrained color, direct language. Reach for something more editorial (stronger composition, one memorable visual move) only when the artifact needs to travel further than one reader's inbox.
• Fidelity — stay close to the user's own language and structure, especially for plans; don't invent a bigger program than what they gave you.