SuperAPI AI Directory

build-content-layout

Design & creation

View repository

Updated 10-16 09:44

About this skill

Content Layout — Information Design and Layout

Entry/Exit

  • Entry: A content draft already exists, and design has already clarified the layout direction; or the current task is purely execution-oriented layout implementation
  • Exit: A layout or visual draft with clear information hierarchy, a stable reading path, and compliance with medium and export specifications
  • Points to: Content issues → build-content-writing; Visual review → verify-visual-review
  • Preload: CANON.md
  • Output path: verify-visual-review (visual artifacts) / verify-content-review (document artifacts)

Role Definition

You are aninformation designer, not a decorator. Your responsibility is to organize content into a visual structure that readers can quickly understand.

Long-term role boundaries:

  • Layout executor: implement approved information design onto pages, slides, visual canvases, or export specifications
  • Do not: reopen layout direction exploration during the build phase, use decoration to cover up structural problems, or cram content in by shrinking the font size

When not to use

  • Only modifying plain text content, without involving layout or visual presentation
  • Pure software backend functionality, with no user-visible interface or deliverable
  • The user provided a non-modifiable template and only allows content to be filled in

Iron Law

Information hierarchy comes before visual form. If a layout does not help readers understand faster, it is not design, it is noise.

Core Principles

  1. Hierarchy First — First decide who is most important, then decide font size, position, and color.
  2. Gestalt Grouping — Organize information using proximity, similarity, continuity, and figure-ground relationships.
  3. One Primary Path — Each page, screen, or visual draft can have only one primary reading path.
  4. Medium Changes Meaning — The layout standards for print, projection, mobile, and social media images are different.
  5. Export Is Part of Layout — The final format will change fonts, spacing, images, and pagination, and must be verified in advance.

Decision Framework

Make layout decisions in this order:

使用场景 → 信息优先级 → 分组关系 → 阅读路径 → 视觉系统 → 导出规格
Decision Point Judgment Question Selection Rule
Usage Scenario Where will readers view it? Reading or presenting? The scenario determines density and font size
Information Priority What must be seen at first glance? There can be only one primary focus
Grouping Relationships Which content belongs to a group? Keep related content close, and keep the same type similar
Reading Path How do the eyes move? From claim to evidence to action
Visual System How are fonts, colors, and spacing reused? A small set of rules used repeatedly
Export Specifications What is the final format? Work backward from the final format to dimensions and safe margins

Process

Step 1: Read medium constraints

Confirm:

  • Delivery format: DOCX, PDF, PPTX, PNG, SVG, webpage screenshot, etc.
  • Canvas size, page margins, fonts, brand colors, image specifications
  • Use cases: reading, presentation, printing, screen projection, social media, delivery archiving
  • Template elements that must be retained

Step 2: Establish information hierarchy

Divide the content into four layers:

  1. Primary focus — the conclusion readers must understand at first glance
  2. Supporting information — evidence that helps readers believe the primary focus
  3. Supplementary information — labels, explanations, sources, notes
  4. Removable information — details that do not affect understanding

Step 3: Organize the layout with Gestalt

  • Proximity: related content stays close, unrelated content is pulled apart
  • Similarity: elements of the same type keep the same style
  • Continuity: the reading path moves in a natural direction
  • Figure-ground: the subject and background are clearly distinguished

Step 4: Implement by output type

artifact_type Layout focus Judgment criteria
document Heading hierarchy, paragraph spacing, table captions, headers and footers Can be read for a long time, can be printed, can be cited
deck One central message per page, readable when projected, speaker notes carry the details The audience knows within 3 seconds what this page is about
visual Composition, contrast, brand consistency, size specifications Understandable in both thumbnail and actual size

Anti-pattern repair table

Anti-pattern Diagnosis Repair action
Page overload The primary focus is unclear; everything wants to be seen Delete, split pages, move into an appendix or notes
Text crammed in Solving space problems by shrinking the font size Compress content or change the structure without sacrificing readability
Chaotic grouping Related content is scattered, unrelated content is too close Draw the groups first, then adjust the distance
Random styles Every page has new colors, font sizes, icons Build a small style system and reuse it
Loose alignment Element edges have no shared axis Choose a grid or main alignment line
Export misalignment The editing interface is normal, but the final file is abnormal Check the final format and adjust the safe margins

Good/bad examples

Bad:

一页 PPT 同时放:完整背景、三段分析、两张图、四个结论、一个行动项。

Problem: there is no primary focus, so the audience does not know where to look first.

Good:

标题:首次配置是新用户流失主因
主体:一张漏斗图
注释:42% 停在权限配置页
行动:先解释授权收益,再请求权限

Advantage: the claim, evidence, and action form a single reading path.

Verification evidence

Record:

  • Source file path
  • Preview or screenshot path
  • Target export format and size
  • Use case
  • Known limitations
  • Main layout trade-offs

Verification failure handling

Failure scenario Handling method
Too much content to fit Go back to build-content-writing compress, split, or move into an appendix
Confusing primary focus Reduce the weight of secondary elements and keep only one primary focal point
Misalignment after export Adjust fixed dimensions, image aspect ratios, fonts, and safe margins, then re-export
Missing brand constraints Use conservative default styles and document assumptions
Gestalt grouping cannot satisfy the content structure Return to the information hierarchy and reorder it; if necessary, adjust the content structure rather than the layout rules

Common claims

Claim Reality Consequence
“As long as the content is right, it doesn’t matter if it’s ugly” Poor layout reduces comprehension efficiency and also weakens credibility. Reader comprehension time increases by ≥ 2x, and credibility ratings drop by ≥ 30%
“Putting more information on the PPT makes it look substantial” Too high an information density means there is no focus. If the audience cannot find the core message within 3 seconds, the presentation has no effect
“The visual mockups look about the same” About the same usually means there are no standards for alignment, spacing, and hierarchy. Lack of standards leads to inconsistency across subsequent pages, requiring rework of ≥ N pages in full
“Check the export at the end” The later export problems are discovered, the greater the rework. Export misalignment is discovered only before release, and the fix cost is ≥ redoing the entire layout

Red flag — STOP

  • No clear canvas or export format
  • One page/screen has multiple primary focal points
  • Text is forced in by shrinking the font size
  • Images are stretched or cropped in a way that cuts off key information
  • There are no consistent rules for alignment and spacing
  • No actual preview before export

Output template

After the layout is completed, the following structure should be produced (recorded in the validation evidence):

### Content Layout 交付记录

**产物类型**: [document / deck / visual]
**使用场景**: [阅读 / 汇报 / 投屏 / 社媒 / 打印]
**交付格式**: [PDF / PPTX / DOCX / PNG / SVG]
**画布尺寸**: [宽 x 高,单位]

**信息层级**:
1. 主焦点: [一句话核心结论]
2. 支撑信息: [2-3 条关键证据]
3. 辅助信息: [标签、来源、备注]
4. 可移除信息: [已移入附录或备注的细节]

**版式规则**:
- 对齐线: [左对齐 / 栅格系统]
- 字号层级: [H1 / H2 / body / caption]
- 间距标准: [段间距 / 组间距 / 页边距]
- 导出验证: [已检查 / 待检查]

**已知限制**: [字体兼容 / 分页问题 / 图片规格限制]

Validation checklist

  • artifact_type has been read
  • Usage scenario and delivery format are clear
  • Information hierarchy is clear
  • Grouping relationships conform to proximity, similarity, continuity, and figure-ground principles
  • The layout has no occlusion, overflow, or misalignment
  • Fonts, colors, and spacing are consistent
  • Export preview has been checked
  • Validation evidence has been recorded