← ClaudeAtlas

html-communicationlisted

Create plans, specifications, write-ups, finding summaries, reports, comparisons, and sets of UI mocks as readable self-contained Hebrew HTML documents with correct right-to-left layout. Use when the user asks to communicate through an HTML document or mentions "HTML" without additional context. Do not use for HTML that will ship as part of a product or codebase.
ShlomiPorush/agent-skills · ★ 2 · Web & Frontend · score 68
Install: claude install-skill ShlomiPorush/agent-skills
# HTML Communication ## Create the document - Work with two files: an editable source, such as `plan.src.html`, and the published file built from it, such as `plan.html`. Choose readable names and keep both across iterations. - The published file is one self-contained `.html` file no larger than 512 KB. Embed all CSS, images, and icons. Do not create companion files or require runtime fetches. - Do not use JavaScript, event handler attributes, forms, frames, `<link>`, or remote resources. YAAPS rejects them. Use CSS-only patterns such as `<details>` when the reader needs to expand something. - Embed images as base64 data URLs of PNG, JPEG, WebP, GIF, or AVIF. Put SVG inline as `<svg>` markup, not as a data URL. - Write all visible prose in Hebrew. Set `<html lang="he" dir="rtl">` and make the page direction right to left. - Implement RTL correctly with CSS logical properties. Isolate English terms, code, URLs, numbers, and other left-to-right fragments with appropriate HTML directionality such as `dir="ltr"`, `<bdi>`, or `<bdo>` when needed. - Write and structure the document like a practical specification, report, or working artifact. Do not style it as a marketing landing page. ## Visual style Every document shares one look. Start each new source from a copy of `assets/document.html` in this skill's directory. - Keep its tokens, fonts, and component classes. Build new components in the same idiom, with the `doc-` class prefix and the `--doc-` tokens. - The accent is th