Red Layout Skill

This skill is the layout source of truth for xiaohongshu-note pages, commonly 1242x1660.

A red-note page should read like a saveable social image note: a strong hook, useful body, and memorable takeaway. The layout should make the viewer understand why the page is worth pausing on and what value they can keep.

This canvas is a social note card, not a compressed slide. When the source content is dense or "needs to be summarized", the model MUST summarize harder here, not cram the full outline into one page. A xiaohongshu page that tries to hold a 16:9 deck's worth of content will overflow no matter how the fonts are tuned.

Deep details live in the references:

• references/catalog.md - named red-note patterns and 1242x1660 zone skeletons.
• references/checklist.md - P0/P1/P2 structural self-check for delivery.

Preflight

Before writing HTML, decide:

1. Stop reason - why would someone pause, save, or screenshot this note page?
2. Hook - title, question, claim, number, or visual anchor in the first 1-2 seconds.
3. Value format - checklist, steps, comparison, myth/fact, template, data takeaway, framework, or story/proof.
4. Body grouping - hard cap 3-4 information chunks (or 5-6 compact list rows for checklist/steps). Anything beyond this MUST be cut, merged, or moved to a separate page — do not squeeze more chunks in by shrinking fonts.
5. Takeaway - conclusion, action, summary line, warning, or compact bottom note.
6. Pattern - choose one structure from references/catalog.md before writing HTML.
7. Budget - estimate hook height, body rows/sections, gaps, bottom note, and safe margin.

Use the canvas dimensions from the prompt. If custom dimensions are supplied, preserve the same red-note reading flow.

Canvas Grammar

• Hierarchy: hook > value body > support > takeaway/source.
• Prefer vertical sections, note cards, list rows, and poster-like bands.
• Keep copy short and scan-friendly. Split long paragraphs into bullets, labeled chunks, or compact rows.
• Use one main data object, framework, or list as the value body.
• Give the lower area a useful role: takeaway, action, summary, source, or final support.
• Use grid/flex document flow for text-bearing modules. Absolute positioning is only for background accents and non-text decoration.
• Capacity ceiling (hard): per page = 1 hook + up to 4 information chunks (or 6 compact rows) + 1 takeaway. A "chunk" is a labeled card, a mini-section, a step, or a row group — not a single bullet. If the outline gives you more points than this ceiling, the page agent resolves overload IN-PAGE by compressing/merging/rewriting into fewer denser chunks; never by shrinking font below the floors, never by splitting into multiple pages.
• Vertical fill (hard): the page must use the full canvas height with no accidental top-stack or bottom gap. The main content wrapper MUST be flex flex-col with at least one flex-1 / flex-grow child absorbing leftover height (typically the body or the takeaway rail), OR use justify-between to spread hook / body / takeaway across the canvas. Never set fixed top padding (pt-[NNpx]) and let content stack from the top while the bottom is empty — that produces an unfinished note. If content is shorter than the canvas, the flex-1 block expands; if longer, you have exceeded the capacity ceiling — compress.
• Body copy, ordinary labels, and card descriptions must be at least 33px (use style="font-size:33px" or text-[33px]); titles/headers must be at least 44px (text-5xl or text-[44px]); auxiliary source/footer text must be at least 22px (text-[22px] or text-2xl). These floors compensate for the much smaller fit-scale a 1660h canvas gets on a landscape presentation screen — default text-lg/text-xl (18px/20px) will be unreadable, do not use them on this canvas.

Pattern Quick Lookup

Use references/catalog.md for the full structure recipe before writing a new or heavily repaired note page.

Note Budget

Calculate before writing:

1. Canvas height: commonly 1660px.
2. Outer vertical padding: commonly 96-176px total.
3. Hook/title zone: usually 220-420px after wrapping.
4. Body sections or list rows: calculate count and row height.
5. Gaps between sections.
6. Bottom takeaway/source/reserve: usually 120-260px when present.
7. Remaining height is the main value zone.

For charts, reserve a specific frame height and keep the @ppt-chart-height=N marker aligned with the h-[Npx] class. Prefer compact bars, mini trends, rank lists, or hero metric + explanation.

Keep visible facts grounded in the source. Do not invent social-proof numbers, quotes, cases, or claims.

Repair And Self-check

• If the hook is weak, rewrite it around a concrete benefit, question, number, or claim.
• If the value body is dense, convert paragraphs into labeled chunks, bullets, rows, or one hero data object.
• If the outline oversupply exceeds the 4-chunk ceiling, resolve overload in this priority: (1) summarize and compress — say the same information in fewer words (long descriptions become short phrases, sentences become single data points; remove water, not information), (2) merge related points into one chunk with a shared label, (3) rewrite a long list as one hero metric + one-line interpretation, (4) switch pattern to a denser format (e.g. comparison matrix, 2x2). Never resolve overload by going below the font floors or by exceeding the canvas height.
• If the note lacks a memory point, add a bottom takeaway or action line.
• If items feel scattered, group them under 2-4 section labels.
• If a chart/list is hard to scan, simplify to a hero metric, compact ranking, or grouped rows.
• Before delivery, run references/checklist.md.