editorial-card-screenshot

name	editorial-card-screenshot
description	Generate high-density editorial HTML info cards in a modern magazine and Swiss-international style, then capture them as ratio-specific screenshots. Use when the user provides text or core information and wants: (1) a complete responsive HTML info card, (2) the design to follow the stored editorial prompt, (3) output in fixed visual ratios such as 3:4, 4:3, 1:1, 16:9, 9:16, 2.35:1, 3:1, or 5:2, or (4) both HTML and a rendered PNG cover/card from the same content.
metadata	{"clawdbot":{"requires":{"bins":["google-chrome","chromium","chrome"]}}}

Editorial Card Screenshot

Overview

Turn source text into a compact, high-contrast HTML information card that follows the user's editorial prompt, then render a screenshot in one of the supported aspect ratios. The goal is not just density but editorial quality: clear hierarchy, strong visual anchors, and screenshot-stable rendering without accidental cropping or dead space.

Always preserve three output stages unless the user explicitly asks to skip one:

1. Write one sentence judging the information density as high, medium, or low.
2. Output the complete HTML with embedded CSS.
3. Self-check that body text remains readable on mobile.

Workflow

1. Analyze Content Density

Read references/content-fit.md. Inventory semantic units, estimate density, and choose layout strategy from both density and ratio:

• Use "big-character" composition when content is sparse and a single phrase, number, or hook can carry the page.
• Use a two-column or three-column editorial grid when content is dense and needs stronger hierarchy.
• Use oversized numbers, heavy rules, tinted blocks, and pull-quote scale to avoid dead space.
• Do not force dense content into evenly weighted tiles. Build primary blocks, secondary blocks, and lighter supporting blocks.
• Match structure to content type:
  • Ranking / recommendation content: allow asymmetric hero + structured list.
  • Tutorial / analysis / interpretation content: group into overview, core judgment, interpretation, boundary, and conclusion.
• Write a short space-allocation plan before final HTML. Assign approximate area to hero, primary module, support area, and footer.
• Do not use the starter template's current arrangement as evidence that it is the right skeleton.

Before compressing content, first change the layout skeleton.

• Ratio changes should primarily change reading path, hierarchy, and module arrangement.
• Do not treat ratio changes as a reason to delete content by default.
• Only compress, group, or summarize when the current ratio cannot hold the content clearly after layout has already been restructured.

2. Apply the Stored Editorial Rules

Use these defaults unless the user overrides them:

• Import Google Fonts:

  <link href="https://fonts.googleapis.com/css2?family=Noto+Serif+SC:wght@700;900&family=Noto+Sans+SC:wght@400;500;700&family=Oswald:wght@500;700&family=Inter:wght@400;600;700&display=swap" rel="stylesheet">
  

• Keep body text at 18px to 20px on a 900px-wide composition.
• Keep meta/tag text at 13px minimum.
• Use compact spacing: container padding 40px to 50px, component gaps 30px to 40px, line-height 1.5 to 1.6.
• Add visual weight with 4px to 6px accent rules, subtle gray planes, and 4% noise overlays.
• Favor #f5f3ed or similar warm-paper backgrounds unless the user supplies another palette.
• Preserve breathing room. Do not shrink outer margins so much that the card loses composure.
• For title zones, prefer larger line-height and clearer separation from subtitle / summary blocks.
• In dense right-side modules, reduce font weight slightly so the page stays clear without feeling heavy.
• Use stronger internal structure inside blocks: subheads, bullets, numbered lines, compare rows, or secondary labels.
• Avoid equal-weight boxes when the card is dense. At least one module should feel visually heavier than the others.
• Avoid making every module use the exact same visual language. Differentiate at least one or two areas through tone, scale, background treatment, or typographic weight.
• Default to a calm editorial mode with selective highlights. If the user asks for stronger expression, you may push toward:
  • Bold: more cover-like, stronger anchors, larger weak-background text, heavier accents.
  • Refined: lighter contrast, quieter accents, more restrained paper-like atmosphere.
  • Hybrid: the recommended default when style is not specified; refined overall with a few bold anchor moments.
• Keep Google Fonts imports, but always provide local fallback stacks so the rendered PNG stays structurally stable when remote fonts fail to load.
• If the user explicitly provides a title, use that exact title as the main headline by default. Only compress or reinterpret it when the user asks or when the ratio cannot hold it clearly after layout changes.
• Put interpretation, summary, and framing in the subtitle / deck / summary fields instead of silently rewriting the main title.
• Do not hard-code personal signatures, creator avatars, or account handles into reusable cards unless the user explicitly asks for branding.

3. Choose the Right Layout Skeleton

Pick ratio-specific structure before writing final copy.

4:3

• Best for full analytical spread or ranked lists.
• Prefer: hero + summary band + dense two-column list + stronger footer.
• Use one main judgment block before the list so the page does not become a flat wall of 10 equal items.
• Recommended reusable skeleton:
  • left heavy primary module for the main process / sequence / framework
  • right narrower stack for takeaways, pitfalls, or judgments
  • a light but intentional source / core-judgment strip at the bottom
• Avoid making 4:3 a symmetrical two-column newspaper wall from top to bottom.

3:4

• Keep the same information ambition, but change the reading path.
• Prefer: title band + insight row + mixed large/small body modules.
• Use mixed scales: one heavy primary block, one or two medium blocks, and smaller support blocks.
• Do not let the whole portrait card collapse into a long single column.
• Recommended reusable skeleton:
  • strong cover-style title zone
  • compact stat strip or insight strip
  • one large primary module
  • one medium judgment module
  • two smaller lower modules for takeaways / pitfalls / examples
• Avoid lower-half layouts that become two large empty boxes with only a few lines of copy.

1:1

• Best for ability map, grouped comparison, or balanced editorial overview.
• Prefer: strong hero + one heavier quadrant + three supporting quadrants + dense footer strip.
• Square layouts should feel centered and modular, not evenly tiled.
• Do not treat 1:1 as the default skeleton for every card. Pick it only when the output ratio is actually square.
• Recommended reusable skeleton:
  • strong title / subtitle hero across the top
  • one compact stat strip
  • one heavy left module for the main framework or sequence
  • one upper-right judgment module
  • one lower-right split for takeaways / pitfalls or compare blocks
  • one thin source / core-judgment strip at the bottom
• Avoid four equal quadrants and avoid tiny typography spread across too many boxes.

Wide covers (3:1, 5:2, 2.35:1)

• Reduce paragraph length aggressively.
• Use fewer but larger blocks, stronger headlines, and short support lines.

16:9

• Prefer a horizontal hero plus one structured support area.
• Keep the comfortable capacity to roughly two to five primary-point equivalents.

9:16

• Use a staged vertical reading path with a compact hero, one dominant middle module, and grouped lower supports.
• Avoid repeating same-height modules down the full canvas.

4. Build HTML for Rendering

When HTML will be screenshotted, design the page as a fixed-size canvas instead of a responsive webpage:

• Match the exact pixel dimensions of the selected ratio preset from references/ratios.md.
• Treat the card as a design board with explicit width and height, not as a fluid 100vw / 100vh layout.
• Remove browser-default margins with html, body { margin: 0; }.
• Make the card itself fill the screenshot viewport exactly.
• Avoid interactions, sticky headers, or long scrolling sections.
• Use fixed pixel wrappers, for example:

  .frame {
    width: 2000px;
    height: 1500px;
  }
  
  .card {
    width: 100%;
    height: 100%;
    padding: 48px;
    background: #f5f3ed;
  }
  

Do not rely on 100vw, 100vh, or responsive container widths as the primary design size for screenshot output.

If the user asks only for HTML, still make the layout screenshot-ready.

At the same time, preserve basic browser preview behavior:

• In screenshot mode, html, body, and the outer frame should match the target canvas size exactly.
• In mobile / narrow-width preview mode, add a media-query fallback that returns the page to normal flow so the HTML is still readable outside the screenshot workflow.

Use these structural heuristics when composing the card:

• Fill the proportion intentionally. Rebalance layout according to width / height instead of scaling one static template.
• In 4:3 landscape, asymmetric left-right layouts often work best for dense analytical content.
• In 3:4 portrait, use portrait-friendly mixed grids rather than a single narrow column.
• Keep title, subtitle, summary, and modules separated by explicit rows or bands so they do not collide.
• When the user supplied the title, protect it as a first-class anchor. Expand the layout around it before you consider shortening or paraphrasing it.
• If using numbered modules, keep numbers visually weak enough that they never collide with titles.
• If a section becomes visually monotonous, introduce contrast through hierarchy changes rather than decorative clutter.
• Let big modules carry richer copy than small modules. Do not give every block the same amount of text.
• Do not use 1fr rows or columns in ways that can create large accidental voids near the footer or push important content to the canvas edge.
• Do not stretch tinted or dark panels to fill unused height. Empty space inside a colored panel reads as an unfinished module, not breathing room.
• If the lower half feels empty, first rebalance module hierarchy or add a stronger bottom band before shrinking text or stretching containers.
• On high-density cards, do not leave a large plain-paper gap between the final module and footer. Reorganize the modules or add a compact conclusion band.
• If a lower module is visually large, give it enough internal structure or a secondary judgment line so it earns the area it occupies.

5. Capture the Screenshot

Use the bundled shell script when the user wants a PNG output:

./scripts/capture_card.sh input.html output.png 3:4

Supported ratios and render sizes live in references/ratios.md.

The rendering helper requires a local Chrome or Chromium binary. It first respects CHROME_BIN when set, then falls back to common binary names and a macOS Chrome app path.

Before running the script:

• Save the generated HTML to a local file.
• Ensure the page is self-contained except for fonts.
• If you keep the default font imports, rendering will request Google Fonts over the network.
• Ensure the HTML uses a fixed-size design canvas that matches the chosen ratio preset.
• Ensure the viewport composition already matches the requested ratio.
• Ensure fallback fonts are declared so layout remains stable even if font downloads fail during headless rendering.

After running the script:

• Open and inspect the PNG.
• Apply every render check in references/content-fit.md.
• Revise the skeleton before changing typography or shortening copy.
• Do not deliver the first render when it contains unexplained empty regions, crowded modules, or cropped content.

If the screenshot still has bottom whitespace after layout has already been improved:

• Keep the default ratio-specific screenshot as the primary output.
• Only when the user explicitly accepts a slight aspect-ratio deviation, run the optional trim helper after rendering.
• Treat trimming as a post-process fix, not as the default rendering behavior.

6. Ratio Policy

Accept only these ratio presets:

• 3:4
• 4:3
• 1:1
• 16:9
• 9:16
• 2.35:1
• 3:1
• 5:2

If the user gives a ratio outside this set, ask them to map it to the nearest supported preset rather than inventing a new one.

Output Contract

When responding to a card-generation request:

• Start with exactly one sentence describing information density.
• Then output complete HTML in one code block.
• If the user also requested an image, state the ratio used and the screenshot command after the HTML.
• Keep prose short; the HTML is the deliverable.

Resources

references/ratios.md

Open this when you need the exact preset names or capture dimensions.

references/editorial-card-prompt.md

Use this as the canonical prompt spec when the user wants the latest validated editorial-card behavior.

references/recommended-skeletons.md

Use this when you want ratio-specific reusable skeletons rather than one-off composition ideas.

references/content-fit.md

Open this before choosing a skeleton and after rendering. It defines semantic-unit density, ratio capacity, space allocation, and rejection checks for empty or crowded cards.

scripts/capture_card.sh

Run this to capture a PNG from a local HTML file using a supported ratio preset. It requires a local Chrome or Chromium binary or an explicit CHROME_BIN override.

scripts/trim_card_bottom.sh

Run this only as an optional post-process when the user accepts a slightly shorter final image in exchange for removing bottom whitespace.

assets/card-template.html

Use this as a starting shell when you want a minimal ratio-ready HTML canvas before filling in real content. The template syncs its canvas size to the active viewport during capture, while still falling back to readable normal flow on narrower browser widths.

Failure Checks

Before finalizing HTML or PNG, explicitly reject the result if any of these happen:

• A user-provided title was silently rewritten even though the ratio could have held it with a better layout.
• The title overlaps, visually collides with, or blocks summary/body content.
• The title becomes a narrow vertical strip when more horizontal width is available.
• Dense cards are split into too many equal-weight boxes.
• Large blocks contain too little copy and read like empty containers.
• The canvas shows large areas of dead space that could be filled by stronger hierarchy, richer block content, or a heavier main module.
• The PNG feels meaningfully emptier than the HTML layout intent.
• The rendered PNG uses a different reading rhythm than the HTML because remote fonts failed and no local fallback stack was provided.
• The footer or bottom band is cropped, or a large bottom whitespace strip appears because the grid sizing pushed content away from the lower edge.
• The bottom-most meaningful content ends above 80% of the canvas height without an intentional low-density cover composition.
• One unexplained empty region occupies roughly more than 20% of the canvas.
• The chosen ratio is over capacity and the card was not grouped, summarized, or split.