article-illustrator

Article Illustrator

Transform the article content into an Anthropic-style flat-design explanatory illustration webpage, convenient for the user to open and screenshot for WeChat official accounts, blogs, or long-form articles.

Core Principles

Illustrations are not decoration, they are explanation tools.

• Illustrations should supplement structures, comparisons, processes, hierarchies, and causality in the article that are hard to see at a glance
• Prefer horizontal images, suitable for embedding in the article body; vertical images are only used for single-card focus or when the content is very narrow
• Use Chinese by default, unless the article itself is in English and aimed at English readers
• Do not write content that can be expressed with graphics as long sentences; when screenshotted it should look like an image, not a document
• Each image expresses only one core judgment; do not cram the entire article into one image
• Text should only retain titles, labels, key numbers, button names, and the point-making sentence
• Labels, descriptions, and point-making sentences do not use quotation marks
• Do not use em dashes

Input

• The article text provided by the user, or a readable file path
• Optional illustration count, size, usage scenario, and special style requirements

If the user has not provided article content, first ask the user to supplement it. When the article is less than 100 characters, remind that the content may be too short, but if the user insists, a single concept image can be made.

Workflow

1. Read the article

Identify this information:

• Article type, such as product introduction, technical documentation, blog, marketing page, retrospective, review
• Number of core viewpoints
• Content suitable for visualization, such as numbers, processes, comparisons, architecture, hierarchy, causality
• Content that does not need illustrations, such as ordinary narration, examples, emotional buildup

2. Choose illustration positions

Judge paragraph by paragraph where an image is truly needed for explanation.

Prioritize these positions:

• The text describes a relationship, but readers need to imagine the structure
• The text describes a process, but the steps are easily confused
• The text makes a comparison, but the differences are not intuitive enough
• The text contains multiple levels, roles, or modules
• The text contains key numbers, and an image can amplify the memory point

Positions not recommended for illustrations:

• Only stating facts
• Only telling a story or giving examples
• Only expressing an attitude
• The image can only repeat the original text and cannot provide additional understanding

3. Whether to give suggestions first

By default, first give illustration suggestions, then wait for user confirmation before generating HTML.

If the user explicitly says do it directly, generate directly, produce it for me, no confirmation needed, skip confirmation and generate directly.

Suggestion format:

配图建议

【图 1】位置：第 X 到 Y 段
解释什么：核心关系或流程
适合图型：左右对比 / 横向流程 / 网格卡片 / 上下分层 / 单卡聚焦
建议比例：横图 / 竖图

【总结】
共 X 张图
优先做图 1，因为它解释文章最关键的概念

4. Generate HTML

Generate a self-contained HTML file, save to:

/Users/gai/Pictures/article-illustration-[timestamp].html

Requirements:

• CSS inline
• No dependency on external JS, images, or font CDNs
• Fonts use local fallback
• Multiple images placed in the same page, each image is an independent screenshot block

5. Acceptance

After generation, check the file:

• HTML file has been created
• Each image has a number and a title
• The content does not wrap ordinary tags in quotation marks
• No dashes are used
• No external resource dependencies
• Colors do not exceed the specified palette
• A single image does not contain excessive text, and the screenshot area is not a long document

Visual system

Canvas

• Background:#FBF8EF
• Margin on all sides: 40px
• Overall flat, no shadows, gradients, 3D, frosted glass, or glow

Palette

Use only the following colors:

• Primary text and dark blocks:#2C2C2A
• Secondary text:#888780
• Abstract horizontal lines:#B4B2A9, 3px rounded caps, opacity 0.6
• Border:#D3D1C7，0.5px
• Beige fill:#E8DCC0
• Light beige fill:#F1EFE8
• Moss green accent:#7A8B5C, used only for meanings such as nature, organic, health, and growth
• Warm orange highlight:#D85A30, appears at most once per image

Fonts

• Serif headings:Tiempos Text, Source Serif Pro, Charter, Georgia, serif，weight 700
• Sans-serif body text:Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, PingFang SC, Microsoft YaHei, sans-serif
• Monospace:ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace
• When small labels are all uppercase,letter-spacing: 2px

Content abstraction

• Paragraphs and descriptive text should preferably be abstracted into gray horizontal lines
• Alternate horizontal line lengths between 100%, 85%, and 70%
• When retaining real text, it must be short, accurate, and screenshot-ready
• A theme statement is optional, no more than 16 Chinese characters or 12 English words

Spacing

• Closely related: 12px
• Within the same group: 24px
• Independent blocks: 40px
• Card padding: 20 to 24px

Geometry

• Small element corner radius: 6px
• Card corner radius: 10 to 12px
• Maximum corner radius: 16px
• Border: 0.5px #D3D1C7
• Single-side border corner radius must be 0

Layout selection

Prefer horizontal images, with width controlled between 800 and 900px.

• Left-right comparison: suitable for two options, two states, or before-and-after changes
• Horizontal flow: suitable for steps, chains, and evolution
• Grid cards: suitable for 3 to 4 parallel concepts
• Top-bottom layering: suitable for system levels and upstream-downstream relationships
• Single-card focus: suitable for one core number, conclusion, or concept
• Four-part narrative: suitable for explanatory long-form content such as pain points, architecture, mechanisms, and conclusions

Use a 4:5 or 3:4 ratio for vertical images. If the content does not fit horizontally, change the layout first rather than making the font size very small.

Layout details

Left-right comparison

• Two columns are symmetrical, equal width, same spacing, and same padding
• Main label font size 13 to 14px, bold, color #2C2C2A
• Secondary description color #888780
• Do not use a thick single-side border to distinguish panels
• Panel backgrounds uniformly use #F1EFE8
• Neutral node backgrounds also use #F1EFE8

Grid cards

• Rows and columns are evenly spaced, and cards are equal width and height
• 4 columns with 24px spacing, 2 to 3 columns with 32px spacing
• The card interior has three parts: mini illustration area, title, and subtitle
• The mini illustration area occupies 45% to 55% of the card height
• Title 18 to 22px, serif bold
• Subtitle 13 to 14px, color #888780

Mini illustration

• Minimalist, usually 3 to 6 basic shapes
• Use only #E8DCC0、#2C2C2A、#D3D1C7
• Green and orange do not go into the diagram unless that card is the highlighted protagonist
• Core diagram elements need short labels; decorative or structural shapes do not need to be labeled one by one
• When it can be explained clearly with text plus simple shapes, do not force-draw icons
• Do not use text to replace results; results should be expressed as much as possible through graphical relationships such as arrows, flow direction, branching, convergence, and blocking

Reference shapes:

• Table: 3x2 grid, first row filled with beige
• Image placeholder: rectangle, mountain-shaped polyline, small circle
• Flow: three small squares and arrows
• Slider: two horizontal lines and two small circles
• Palette: 4 small squares in a horizontal row
• Chart: L-shaped axes and scatter points
• Code: dark rectangle and several gray horizontal lines
• Dialogue: two rounded rectangles
• Interruption: square grid and diagonal lines
• Expansion: circle, pointer, spreading circles
• Division of labor: three squares of different shades

Flowchart

• Expand horizontally in a single line as much as possible
• Node content should be concise, 2 to 4 characters
• Connect nodes with arrow characters
• Neutral nodes use #F1EFE8 background and #D3D1C7 thin border
• Only functional nodes use orange or green highlighting
• Keep the color system consistent within the same panel

Output contract

The final reply includes:

• Absolute path of the HTML file
• A brief explanation telling the user to open the HTML and take a screenshot
• If some candidate images were skipped, explain why

Do not output large blocks of HTML content to the chat window.

Failure handling

• No article content: ask the user to provide the article text or file path
• File path unreadable: explain that reading failed and ask the user to provide it again
• Content too short: indicate that it may only be suitable for making one concept diagram
• User changes content midway: reread the article, then choose the image placement again