answer-me-with-html Checked

• 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.

2. Choose components by the shape of the information (see section 4).

3. 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

4. Read the output:

• ✓ <path>: success. Whether the browser opens automatically depends on the user's settings (am config); --no-open affects only this run. A page with STE or code warnings never opens automatically.
• ✗ L<line> [component] … + Correct example:: fix that line following the example, then render again (no page was written).
• code n warnings: a code block is longer than 40 lines, or a diff hunk has a different number of lines than its @@ header says. Cut the block or fix the header to the lines that make the point and render again, or keep it if every line matters.
• STE n warnings: rewrite the flagged lines as suggested, then render again. Retry at most 2 rounds; if warnings remain, keep the last page and say so.
• Every time you render again after a ✓, add --replace <path from the last ✓ line>. The CLI deletes that page once the new one is written, so one answer leaves one page.
• ! 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.

5. 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.

If the render output has a link: line, the user runs am serve: use that URL as the page link instead, with the URL as the label too, and skip the file:// link below. Never start am serve yourself; only the user starts it.

Otherwise 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