owwzo/ai-agent/answer-me-with-html

Answer me with HTML: answer a complex question with one HTML page

You write only the content draft (extended Markdown). The am CLI does all layout, colours, dark mode and diagram coordinates. Do not hand-write HTML / CSS / SVG.

Reply to the user, and write the draft, in the user's language.

0. When the user wants to change settings

Arguments for this call: $ARGUMENTS

When the arguments start with config (for example /answer-me-with-html config open off), this turn handles settings only and produces no page:

• config: run am config to show the current settings, then let the user choose. Where the agent has a choice tool such as AskUserQuestion, use it: at most 4 settings at a time, these first: open, theme, mode, style, with the current value marked in the options. Otherwise ask in plain text.
• config <key> <value>: run am config set <key> <value>.
• config reset [key]: run am config reset [key].

When the user asks in natural language ("stop opening the browser", "use the card theme by default"), also convert it to am config set. Settings: open (auto-open the browser), theme, mode, style, voice (video narration), update_check (new-version notices). Run am config to see all descriptions.

When the arguments start with clean, or the user asks to clean up pages / the cache: first run am clean --dry-run and tell the user how many items and how much space will be deleted. Run am clean only after the user agrees (add --all to delete all pages and videos, --days N to change how many days to keep).

When the arguments start with update, or the user asks to update this skill: update according to how it was installed. Installed with npx skills: run npx skills update answer-me-with-html -y. Installed as a Claude Code plugin: run claude plugin update answer-me-with-html@answer-me-with-html (or ask the user to click Update now in /plugin → Installed), then ask the user to run /reload-plugins. Installed with git clone: run git pull && npm install in the repository directory.

1. Decide: produce a page or not

Produce a page if any of these is true:

• There are ≥3 interrelated concepts, and the reader needs to see how they relate.
• There is a flow, protocol, call chain or state transition (especially with branches or several actors).
• There is a comparison across ≥3 dimensions, a trade-off between options, or a "can / cannot" list.
• There is a hierarchy or an evolution over time.

Otherwise answer in plain text. When unsure: the more the question "needs a picture to understand", the more it calls for a page.

Always-on mode

If the context contains the [answer-me-with-html always-on] reminder (the user added the always-on rule to a rules file such as CLAUDE.md or AGENTS.md), the bar is lower:

• Whenever this turn gives a conclusion, summary, plan, comparison, review or explanation, attach a page.
• Do not skip it because "the answer is short". If there is a conclusion, produce a page.
• For everyday conclusions use a small page with 2–4 panels: one callout with the conclusion, plus one table or one diagram. Do not add panels just to fill space.
• Render with --no-open, so no browser window interrupts the user. The user opens the page by clicking the path at the end of the reply.
• Order: render the page first, then write the text reply. The reply is the last thing in the turn, with the page link on its last line (see step 5). Do not write the reply and then call am render.
• Produce no page for small talk, one or two sentences with no conclusion, pure command output, or when the user asks for plain text.

2. Workflow (one Bash call)

The CLI is bundled in this skill's directory: scripts/am.mjs, a single file with no dependencies to install; it needs only Node.js 20+. Below, am always means:

node "${CLAUDE_SKILL_DIR}/scripts/am.mjs"

In Claude Code, the path above is replaced with this skill's directory automatically. If you see the variable unreplaced (other agents), replace it with the absolute path of the directory that contains this SKILL.md. If the user installed the am command globally, you can also use am directly.

1. First list 3–8 panels in your head. Each panel answers one sub-question only.

The draft language follows the language of the user's question: an English question gets an English draft, a Chinese question a Chinese draft, a Japanese question a Japanese draft. The page button labels, <html lang> and the STE check rules switch automatically by the draft language (a draft containing kana counts as Japanese); STE applies the English or Chinese rules to each sentence by its language (Japanese sentences get only the sentence-length and paragraph-length checks, with the same character limits as Chinese; any other language gets only those two checks, counted in words). To set the language yourself, write lang: in the frontmatter: en, zh (Simplified Chinese), zh-Hant or zh-TW (Traditional Chinese), ja, or any other language tag such as fr or ko. Detection reads Chinese (Simplified, or Traditional when the text has characters written in only one form), Japanese, Korean, and Cyrillic, Arabic, Hebrew, Thai and Greek text, and reads all Latin-script text as English. Declare the language when the user writes a Latin-script language other than English, when a Chinese text is too short or too plain to show Traditional characters, or when an exact tag matters (Arabic script also writes Persian, Cyrillic also Ukrainian). A language without its own labels still gets the right <html lang>, with English page labels.

1. Choose components by the shape of the information (see section 4).
2. Render in one go with a heredoc:

node "${CLAUDE_SKILL_DIR}/scripts/am.mjs" render - <<'AM_EOF'
---
title: Title
---
## A Panel title

A -> B: label

AM_EOF

1. Read the output:

• ✓ <path>: success. Whether the browser opens automatically depends on the user's settings (am config); --no-open affects only this run.
• ✗ L<line> [component] … + Correct example:: fix that line following the example, then render again.
• STE n warnings: rewrite the flagged lines as suggested, then render again. Retry at most 2 rounds; if warnings remain, keep the page and say so.
• ! Cleanup hint: … or ! Update hint: …: pass it on to the user in one sentence at the end of the reply, and ask whether to clean up / update. Do not run am clean or the update command yourself; wait until the user agrees. The CLI throttles these: the cleanup hint appears at most once every 7 days, the update hint at most once every 3 days.

1. Reply in the terminal with only 2–3 lines: one core conclusion + the page link. Do not paste the draft or the HTML back into the terminal. Write this reply after the render, as the last step of the turn: render the page first, then reply. No tool call comes after the reply.

Write the page link as a Markdown link to a file:// URL, with the URL as the label too: [file:///abs/path.html](file:///abs/path.html). Take the absolute path from the ✓ line and add file:// in front; do not percent-encode it. GUI hosts (Codex, Antigravity) render this as a clickable link, and a terminal still shows the full URL.

When a page already exists and only one panel needs to change, do not rewrite the whole page. Take the source draft from the HTML's #am-source, replace only the matching ## section, and overwrite the page in place:

node "${CLAUDE_SKILL_DIR}/scripts/am.mjs" patch page.html --panel "Panel title" <<'AM_EOF'
## A Panel title
New content
AM_EOF

--panel matches the title, the letter ID, or ID title. If the panel is not found or the page has no #am-source, leave the file unchanged. patch keeps the original page's theme, light/dark mode and STE style; add --theme / --mode / --style to change them. Full usage: am help patch.

3. Draft format quick reference

---
template: sheet     # sheet board (default, one-screen overview) | doc linear explanation (read step by step)
theme: auto         # auto (default): paper for doc or text-only drafts, blueprint with diagrams | blueprint | shadcn | paper | a theme the user made (am list shows it)
title: Title
subtitle: One-line summary     # optional
cols: 3             # most columns in a sheet row, default 3
source: RFC 9293    # any other key is shown in the page header's meta line
---
Lead: one or two sentences with the core conclusion (optional).
 
## A Panel title {span=2 meta="small text, top right"}
Plain Markdown: paragraphs, lists, tables, quotes.
Table status words: ok / no / warn (may carry text: "ok approved") → ✓ / ✗ / ! badges.
 
## B {bare}            ← bare: no title bar (suits a kv title block)

• The panel letter ID can be omitted; it is assigned automatically.
• ``html / ``svg fenced blocks are embedded as-is. Use them only when no component can express the content.
• Full reference: am help format; component syntax: am help <component>; component list: am list.

4. Choose components by the shape of the information

Selection rules:

• Conclusion first. The first panel or the lead gives the core answer; the following panels give the evidence.
• One panel, one question. With more than 8 panels, split the page or cut panels.
• span is a hint. In a browser the sheet sizes each panel to its content and fills every row, so write no span for a wide table or diagram. Write span only for a panel that must stand out (span = cols gives it a row of its own). rows applies only to the plain grid (without JavaScript, in print and on narrow screens); the browser layout ignores it.
• Do not invent data. Without real numbers, do not use limits; mark illustrative data as "illustrative" in the description.

5. STE controlled writing (the text in the draft)

am render checks automatically and only warns by default (style: 80); with style: strict a draft that fails produces no page; style: off turns the check off.