AGENT SKILL

html-communication

Use when the user asks to communicate through an HTML document, or mentions "HTML" with no other context. Covers plans, specs, write-ups, findings, summaries, reports, comparisons, and UI mockups shown as readable HTML.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
html-communication
description
Use when the user asks to communicate through an HTML document, or mentions "HTML" with no other context. Covers plans, specs, write-ups, findings, summaries, reports, comparisons, and UI mockups shown as readable HTML.

03 SKILL.md 正文

HTML Communication

When to Use

Use this skill when the user wants a plan, spec, write-up, findings, summary, report, comparison, or set of UI mockups presented as readable HTML.

Do not use it for HTML that ships as part of a product.

Document

Create one self-contained HTML file.

  • Write it like a spec, not a landing page: dense, scannable, no hero section, no decorative chrome, no marketing voice, no em dashes.
  • Default to a readable dark theme: a dark gray background (not pure black), light text with high contrast, and restrained accent colors. If the user names a color or style, follow it.
  • Make it readable on a phone: use a responsive viewport and no fixed-width layout.
  • Use semantic HTML, inline CSS, inline SVG, and data-URL images. Do not load images from remote URLs.
  • Use an inline classic script only when interactivity materially helps. The page must still be useful without JavaScript.
  • Give external links target="_blank" and rel="noopener noreferrer".

Never include secrets in the document.

UI Mocks

When the user asks for variants:

  • Render real styled variants, not descriptions.
  • Label them A, B, C, and so on, so the user can pick one by letter.
  • Lay them out side by side for direct comparison.

Output

Plans come from Markdown first:

  1. Write or update the Markdown plan in the project's .plans/ folder, named YYYY-MM-DD-short-slug.md. If the plan already exists, use that file.
  2. Create the HTML from that Markdown file. The HTML must show the same content as the Markdown.
  3. Save the HTML next to the plan with the same name and an .html extension, for example 2026-10-08-auth-retry.html.

Other documents go straight to HTML. Save them in the project's .plans/ folder as YYYY-MM-DD-short-slug.html.

Create .plans/ if it does not exist. To revise, update the same file. Create a new file only when the user asks for a new draft. For a plan, update the Markdown first, then regenerate the HTML.

Report the absolute local path to the HTML as a clickable link.

Do not open a browser unless the user asks.

04 同仓库更多 Skills