Baoyu Infographic

Infographic Generator

Two dimensions: layout (information structure) × style (visual aesthetics). Freely combine any layout with any style.

User Input Tools

When this skill prompts the user, follow this tool-selection rule (priority order):

1. Prefer built-in user-input tools exposed by the current agent runtime — e.g., AskUserQuestion, request_user_input, clarify, ask_user, or any equivalent. 2. Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question. 3. Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order.

Concrete AskUserQuestion references below are examples — substitute the local equivalent in other runtimes.

Image Generation Tools

When this skill needs to render an image, resolve the backend in this order:

1. Current-request override — if the user names a specific backend in the current message, use it. 2. Saved preference — if EXTEND.md sets preferred_image_backend to a backend available right now, use it. 3. Auto-select (when the preference is auto, unset, or the pinned backend isn't available):

• Codex (`imagegen`) — first, inspect your available-skills / tool inventory. If a skill named imagegen is listed, you are running inside Codex and MUST use it: invoke via the Skill tool with skill: "imagegen", passing the saved prompt file's content (plus output path and aspect ratio per Codex imagegen's own args). Codex imagegen is the official raster backend in that runtime and outranks any non-native skill (e.g., baoyu-image-gen) unless the user has explicitly pinned a different preferred_image_backend.
• Codex via `codex exec` (`codex-imagegen`) — if the current runtime exposes no native imagegen skill but the codex CLI is on PATH with an active codex login, route through baoyu-image-gen --provider codex-cli (preferred), or — if baoyu-image-gen is unavailable — invoke the bundled wrapper directly. Details, parameters, and the runtime-discovery procedure live in references/codex-imagegen.md — load that file only when this branch is selected.
• Cursor (`GenerateImage`) — if the runtime exposes a native GenerateImage tool, you are running inside Cursor and it outranks any non-native skill the same way Codex imagegen does. Two hard caveats: (a) it has no aspect-ratio parameter — state the target aspect ratio / dimensions explicitly in the prompt text passed as description; (b) it does not accept an output directory — it saves to a tool-managed location, so after generation copy/move the file to the skill's expected output path (e.g., outputs/.../NN-xxx.png). Reference images go in reference_image_paths.
• Other runtime-native tools — if the runtime exposes a different native image tool (e.g., Hermes image_generate), use it the same way.
• Otherwise, if exactly one non-native backend is installed (e.g., baoyu-image-gen), use it.
• Otherwise (multiple non-native backends with no runtime-native tool), ask the user once — batch with any other initial questions.

4. If none are available, tell the user and ask how to proceed.

⛔ Never substitute SVG, HTML, canvas, or other code-based rendering for raster image generation. Codex imagegen's own description says it should be used "when the output should be a bitmap asset rather than repo-native code or vector." If you cannot resolve a raster backend via step 3, fall through to step 4 and ask the user — do not silently emit SVG, write inline <svg> markup, or produce HTML/CSS art as a substitute. This applies even if the article/section seems "diagram-like": the consumer skill calling this rule has already decided that a raster image is what it needs.

⛔ Never repair rendered text by painting over a generated bitmap. Do not use ImageMagick, Pillow, Canvas, SVG, HTML/CSS, OCR scripts, or any other programmatic overlay to cover, rewrite, erase, stroke, or replace labels, headings, callouts, data values, or any other text inside an already generated infographic. If text is wrong or unclear, regenerate from a corrected prompt, switch to a layout with less on-image text, or ask the user which imperfect candidate to keep.

Setting preferred_image_backend: ask forces the step-3 prompt every run regardless of available backends. Users change the pinned backend via the ## Changing Preferences section below.

Prompt file requirement (hard): write each image's full, final prompt to a standalone file under prompts/ (naming: NN-{type}-[slug].md) BEFORE invoking any backend. The backend receives the prompt file (or its content); the file is the reproducibility record and lets you switch backends without regenerating prompts.

Concrete tool names (imagegen, GenerateImage, image_generate, baoyu-image-gen) above are examples — substitute the local equivalents under the same rule.

Reference Images

Users may supply reference images to guide style, palette, composition, or subject.

Intake: Accept via --ref <files...> or when the user provides file paths / pastes images in conversation.

• File path(s) → copy to refs/NN-ref-{slug}.{ext} alongside the output
• Pasted image with no path → ask the user for the path (per the User Input Tools rule above), or extract style traits verbally as a text fallback
• No reference → skip this section

Usage modes (per reference):

Record in `prompts/infographic.md` frontmatter when refs exist:

references:
  - ref_id: 01
    filename: 01-ref-brand.png
    usage: direct

At generation time:

• Verify each referenced file exists on disk
• If usage: direct AND the chosen backend accepts reference images (e.g., baoyu-image-gen via --ref) → pass the file via the backend's ref parameter
• Otherwise → embed extracted style/palette traits in the prompt text

Confirmation Policy

Default behavior: confirm before generation.

• Treat explicit skill invocation, a file path, a matched keyword shortcut, EXTEND.md defaults, and the documented default combination as recommendation inputs only. None of them authorizes skipping confirmation.
• Do not start Step 5 or Step 6 until the user confirms the combination/aspect/language/backend choices.
• Skip confirmation only when the current request explicitly says to do so, for example: --no-confirm, "直接生成", "不用确认", "跳过确认", "按默认出图", or equivalent wording.
• If confirmation is skipped explicitly, state the assumed combination/aspect/language/backend in the next user-facing update before generating.

Options

Layout Gallery (21)

Full definitions live at references/layouts/<layout>.md.

Style Gallery (22)

Full definitions live at references/styles/<style>.md.

Recommended Combinations

Default combination: bento-grid + craft-handmade (fallback recommendation only — per the Confirmation Policy, defaults never bypass Step 4).

Keyword Shortcuts

When the user's input contains these keywords, use the mapped layout as the leading Step 3 recommendation and promote the listed styles to the top of the Step 3 list. Skip content-based layout inference for matched keywords. Append any Prompt Notes to the Step 5 prompt.

Output Structure

infographic/{topic-slug}/
├── source-{slug}.{ext}
├── analysis.md
├── structured-content.md
├── prompts/infographic.md
└── infographic.png

Slug: 2-4 words kebab-case from topic. Conflict: append -YYYYMMDD-HHMMSS.

Core Principles

• Preserve source data faithfully—no summarization or rephrasing (but strip any credentials, API keys, tokens, or secrets before including in outputs)
• Define learning objectives before structuring content
• Structure for visual communication (headlines, labels, visual elements)

Workflow

Step 1: Setup & Analyze

1.1 Load Preferences (EXTEND.md)

Check EXTEND.md in priority order — the first one found wins:

EXTEND.md supports: preferred layout/style, default aspect ratio, language preference, preferred image backend, custom style definitions.

Schema: references/config/preferences-schema.md

1.2 Analyze Content → `analysis.md`

1. Save source content (file path or paste → source.md)

• Backup rule: If source.md exists, rename to source-backup-YYYYMMDD-HHMMSS.md

2. Analyze: topic, data type, complexity, tone, audience 3. Detect source language and user language 4. Extract design instructions from user input 5. Save analysis

• Backup rule: If analysis.md exists, rename to analysis-backup-YYYYMMDD-HHMMSS.md

See references/analysis-framework.md for detailed format.

Step 2: Generate Structured Content → structured-content.md

Transform content into infographic structure: 1. Title and learning objectives 2. Sections with: key concept, content (verbatim), visual element, text labels 3. Data points (all statistics/quotes copied exactly) 4. Design instructions from user

Rules: Markdown only. No new information. Preserve data faithfully. Strip any credentials or secrets from output.

See references/structured-content-template.md for detailed format.

Step 3: Recommend Combinations

3.1 Check Keyword Shortcuts first: If user input matches a keyword from the Keyword Shortcuts table, use the associated layout as the leading recommendation and prioritize associated styles as top recommendations. Skip content-based layout inference.

3.2 Otherwise, recommend 3-5 layout×style combinations based on:

• Data structure → matching layout
• Content tone → matching style
• Audience expectations
• User design instructions

Step 4: Confirm Options

Hard gate: this step is mandatory per the Confirmation Policy — Steps 5–6 cannot start until the user confirms here (or explicitly opts out with --no-confirm / equivalent in the current request).

Ask the user to confirm the questions below following the User Input Tools rule at the top of this file (batch into one call if the runtime supports multiple questions; otherwise ask one at a time in priority order).

Step 5: Generate Prompt → prompts/infographic.md

Backup rule: If prompts/infographic.md exists, rename to prompts/infographic-backup-YYYYMMDD-HHMMSS.md

Combine: 1. Layout definition from references/layouts/<layout>.md 2. Style definition from references/styles/<style>.md 3. Base template from references/base-prompt.md 4. Structured content from Step 2 5. All text in confirmed language

Aspect ratio resolution for {{ASPECT_RATIO}}:

• Named presets → ratio string: landscape→16:9, portrait→9:16, square→1:1
• Custom W:H ratios → use as-is (e.g., 3:4, 4:3, 2.35:1)

Step 6: Generate Image

1. Resolve the backend per the ## Image Generation Tools rule at the top of this file. 2. Ensure the full final prompt is persisted at prompts/infographic.md (already written in Step 5) BEFORE invoking the backend — the file is the reproducibility record. 3. Check for existing file: Before generating, check if infographic.png exists

• If exists: Rename to infographic-backup-YYYYMMDD-HHMMSS.png

4. Call the chosen backend with the prompt file and output path.

• `codex-imagegen` invocation: when the rule resolves to codex-imagegen, see references/codex-imagegen.md for the invocation contract (preferred baoyu-image-gen --provider codex-cli path, runtime wrapper discovery, parameter notes, stdout schema, batch semantics).

5. On failure, auto-retry once

Text correction policy:

• If labels, headings, callouts, data values, or any other rendered text is misspelled, garbled, hard to read, or visually weak, do not patch the bitmap with code.
• For text-correction regenerations, write a new prompt file and a new output path so the flawed candidate is preserved for comparison.
• Post-processing is limited to crop, resize, compression, or format conversion that does not alter text or the main composition.

Step 7: Output Summary

Report: topic, layout, style, aspect, language, image backend, output path, files created.

References

• references/analysis-framework.md - Analysis methodology
• references/structured-content-template.md - Content format
• references/base-prompt.md - Prompt template
• references/layouts/<layout>.md - 21 layout definitions
• references/styles/<style>.md - 21 style definitions

Changing Preferences

EXTEND.md lives at the first matching path in Step 1.1. Three ways to change it:

• Edit directly — open EXTEND.md and change fields. Full schema: references/config/preferences-schema.md.
• Reconfigure interactively — delete EXTEND.md (or ask "reconfigure baoyu-infographic preferences" / "重新配置"). The next run re-triggers first-time setup.
• Common one-line edits:
• preferred_image_backend: auto — default; runtime-native tool wins, falls back to the only installed backend, asks only if multiple non-native are present.
• preferred_image_backend: codex-imagegen — pin to Codex's built-in.
• preferred_image_backend: baoyu-image-gen — pin to the baoyu-image-gen skill.
• preferred_image_backend: ask — confirm backend every run.
• preferred_layout: dense-modules, preferred_style: morandi-journal, preferred_aspect: portrait, language: zh — shift the Step-3 recommendations and Step-4 defaults (per Confirmation Policy, these never bypass Step 4).

Infographic Content Analysis Framework

Deep analysis framework applying instructional design principles to infographic creation.

Purpose

Before creating an infographic, thoroughly analyze the source material to:

• Understand the content at a deep level
• Identify clear learning objectives for the viewer
• Structure information for maximum clarity and retention
• Match content to optimal layout×style combinations
• Preserve all source data verbatim

Instructional Design Mindset

Approach content analysis as a world-class instructional designer:

Analysis Dimensions

1. Content Type Classification

2. Learning Objective Identification

Every infographic should have 1-3 clear learning objectives.

Good Learning Objectives:

• Specific and measurable
• Focus on what the viewer will understand, not just see
• Written from the viewer's perspective

Format: "After viewing this infographic, the viewer will understand..."

3. Audience Analysis

4. Complexity Assessment

5. Visual Opportunity Mapping

Identify what can be shown rather than told:

6. Data Verbatim Extraction

Critical: All factual information must be preserved exactly as written in the source.

Never:

• Round numbers
• Paraphrase quotes
• Substitute simpler words
• Add implied information
• Remove context that affects meaning

Output Format

Save analysis results to analysis.md:

---
title: "[Main topic title]"
topic: "[educational/technical/business/creative/etc.]"
data_type: "[timeline/hierarchy/comparison/process/etc.]"
complexity: "[simple/moderate/complex]"
point_count: [number of main points]
source_language: "[detected language]"
user_language: "[user's language]"
---

## Main Topic
[1-2 sentence summary of what this content is about]

## Learning Objectives
After viewing this infographic, the viewer should understand:
1. [Primary objective]
2. [Secondary objective]
3. [Tertiary objective if applicable]

## Target Audience
- **Knowledge Level**: [Beginner/Intermediate/Expert]
- **Context**: [Why they're viewing this]
- **Expectations**: [What they hope to learn]

## Content Type Analysis
- **Data Structure**: [How information relates to itself]
- **Key Relationships**: [What connects to what]
- **Visual Opportunities**: [What can be shown rather than told]

## Key Data Points (Verbatim)
[All statistics, quotes, and critical facts exactly as they appear in source]
- "[Exact data point 1]"
- "[Exact data point 2]"
- "[Exact quote with attribution]"

## Layout × Style Signals
- Content type: [type] → suggests [layout]
- Tone: [tone] → suggests [style]
- Audience: [audience] → suggests [style]
- Complexity: [level] → suggests [layout density]

## Design Instructions (from user input)
[Any style, color, layout, or visual preferences extracted from user's steering prompt]

## Recommended Combinations
1. **[Layout] + [Style]** (Recommended): [Brief rationale]
2. **[Layout] + [Style]**: [Brief rationale]
3. **[Layout] + [Style]**: [Brief rationale]

Analysis Checklist

Before proceeding to structured content generation:

• [ ] Have I read the entire source document?
• [ ] Can I summarize the main topic in 1-2 sentences?
• [ ] Have I identified 1-3 clear learning objectives?
• [ ] Do I understand the target audience?
• [ ] Have I classified the content type correctly?
• [ ] Have I extracted all data points verbatim?
• [ ] Have I identified visual opportunities?
• [ ] Have I extracted design instructions from user input?
• [ ] Have I recommended 3 layout×style combinations?

Create a professional infographic following these specifications:

Image Specifications

• Type: Infographic
• Layout: {{LAYOUT}}
• Style: {{STYLE}}
• Aspect Ratio: {{ASPECT_RATIO}}
• Language: {{LANGUAGE}}

Core Principles

• Follow the layout structure precisely for information architecture
• Apply style aesthetics consistently throughout
• If content involves sensitive or copyrighted figures, create stylistically similar alternatives
• Keep information concise, highlight keywords and core concepts
• Use ample whitespace for visual clarity
• Maintain clear visual hierarchy

Text Requirements

• All text must match the specified style treatment
• Main titles should be prominent and readable
• Key concepts should be visually emphasized
• Labels should be clear and appropriately sized
• Use the specified language for all text content

Layout Guidelines

{{LAYOUT_GUIDELINES}}

Style Guidelines

{{STYLE_GUIDELINES}}

---

Generate the infographic based on the content below:

{{CONTENT}}

Text labels (in {{LANGUAGE}}): {{TEXT_LABELS}}

codex-imagegen Wrapper Invocation

Load this reference only when the Image Generation Tools rule has resolved to codex-imagegen — i.e., the current runtime exposes no native imagegen skill but codex CLI is on PATH with an active codex login.

Preferred path: route through baoyu-image-gen

If the baoyu-image-gen skill is available in this runtime, always invoke through it rather than calling the wrapper directly. It handles retry/cache/batch/EXTEND.md preferences uniformly with every other provider.

${BUN_X} <baoyu-image-gen-base>/scripts/main.ts \
  --provider codex-cli \
  --image <ABSOLUTE_output> \
  --promptfiles <ABSOLUTE_prompts/infographic.md> \
  --ar <ratio> \
  [--ref <ABSOLUTE_file>]...

Resolve <baoyu-image-gen-base> the same way you resolve any sibling skill — through your runtime's skill registry (Skill tool, plugin marketplace, or $HOME/.baoyu-skills/baoyu-image-gen/).

Fallback: spawn the wrapper directly

Only when baoyu-image-gen is NOT installed in the current runtime. Discover the wrapper's location at runtime — do NOT hard-code ../../packages/... from this skill:

1. Honor explicit override: if $BAOYU_CODEX_IMAGEGEN_BIN is set and points to a real file, use that path. It may be .ts (spawn bun <path>) or .sh/binary (spawn directly). 2. Search the plugin root: walk up from this skill's directory looking for packages/baoyu-codex-imagegen/src/main.ts. If found, that is the wrapper. Spawn it with bun. 3. Last resort: tell the user that codex-imagegen is not available in this runtime and ask whether to install the baoyu-skills plugin (or set BAOYU_CODEX_IMAGEGEN_BIN) or pick another backend.

Once located, the invocation shape is:

bun <WRAPPER>/main.ts \
  --image <ABSOLUTE_output> \
  --prompt-file <ABSOLUTE_prompts/infographic.md> \
  --aspect <ratio> \
  [--ref <ABSOLUTE_file>]... \
  [--timeout <ms>] \
  [--cache-dir ~/.cache/baoyu-codex-imagegen] \
  [--log-file <ABSOLUTE_jsonl_log_path>]

If bun is missing, npx -y bun <WRAPPER>/main.ts ... works as a fallback.

Parameter notes

• All filesystem inputs are auto-resolved against process.cwd() when relative, but agents should pass absolute paths to be robust against cwd drift.
• `--timeout` defaults to 300000 (5 min) per codex exec attempt. Raise (e.g. --timeout 600000 for 10 min) on slow networks or large prompts.
• `--cache-dir` is off by default. Enable for repeatable runs to skip redundant generations of the same prompt+aspect+refs.
• Authentication: the wrapper uses the user's Codex subscription — no OPENAI_API_KEY is read or sent.

Stdout contract

Single JSON line:

• Success: {"status":"ok","path":"...","bytes":N,"elapsed_seconds":N,"thread_id":"...","attempts":N,"cached":bool,...}
• Failure: {"status":"error","path":"...","bytes":0,"error":"...","error_kind":"..."}

error_kind values: codex_not_installed, invalid_args, prompt_file_missing, spawn_failed, timeout, no_image_gen_tool_use, output_missing, invalid_png, agent_refused, lock_busy.

On retryable errors (timeout, spawn_failed, no_image_gen_tool_use, output_missing, invalid_png, agent_refused), ask the user whether to retry or fall back to another backend.

Batch semantics

• Codex image_gen returns one image per call (n=1 only). Multi-image jobs must dispatch one wrapper call per image.
• The wrapper does NOT accept a --sessionId flag. Chain/scene consistency must come from --ref reference images.
• --size and --quality are silently ignored — Codex picks pixel dimensions from --aspect.

First-Time Setup

Overview

When no EXTEND.md is found, guide the user through preference setup before generating any infographic. Saved preferences shift Step-3 recommendations and Step-4 defaults only — they never bypass Step 4 confirmation (see the ## Confirmation Policy section in SKILL.md).

⛔ BLOCKING OPERATION: This setup MUST complete before ANY other workflow steps. Do NOT:

• Ask about source content or topic
• Ask about layout, style, or aspect
• Begin Step 1.2 content analysis

ONLY ask the questions in this setup flow, save EXTEND.md, then continue to Step 1.2.

Setup Flow

No EXTEND.md found
        │
        ▼
┌─────────────────────┐
│ AskUserQuestion     │
│ (all questions)     │
└─────────────────────┘
        │
        ▼
┌─────────────────────┐
│ Create EXTEND.md    │
└─────────────────────┘
        │
        ▼
    Continue to Step 1.2

Questions

Language: Use the user's input language for question text. Do not always default to English.

Use a single AskUserQuestion with multiple questions (the runtime auto-adds an "Other" option):

Question 1: Preferred Layout

header: "Layout"
question: "Default layout preference?"
options:
  - label: "Auto-select (Recommended)"
    description: "Pick layout per content in Step 3"
  - label: "bento-grid"
    description: "Multiple topics, overview (general default)"
  - label: "linear-progression"
    description: "Timelines, processes, tutorials"
  - label: "dense-modules"
    description: "High-density modules, data-rich guides"

Question 2: Preferred Style

header: "Style"
question: "Default visual style preference?"
options:
  - label: "Auto-select (Recommended)"
    description: "Pick style per tone in Step 3"
  - label: "craft-handmade"
    description: "Hand-drawn, paper craft (general default)"
  - label: "corporate-memphis"
    description: "Flat vector, vibrant"
  - label: "morandi-journal"
    description: "Hand-drawn doodle, warm Morandi tones"

Question 3: Preferred Aspect

header: "Aspect"
question: "Default aspect ratio?"
options:
  - label: "Auto-select (Recommended)"
    description: "Pick per layout in Step 4"
  - label: "landscape"
    description: "16:9 (slides, blogs, web)"
  - label: "portrait"
    description: "9:16 (mobile, social, dense modules)"
  - label: "square"
    description: "1:1 (social, thumbnails)"

Question 4: Language

header: "Language"
question: "Output language for infographic text?"
options:
  - label: "Auto-detect (Recommended)"
    description: "Match source content language"
  - label: "zh"
    description: "Chinese (中文)"
  - label: "en"
    description: "English"

Question 5: Save Location

header: "Save"
question: "Where to save preferences?"
options:
  - label: "Project"
    description: ".baoyu-skills/ (this project only)"
  - label: "User"
    description: "~/.baoyu-skills/ (all projects)"

Save Locations

XDG path (${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-infographic/EXTEND.md) is also recognized at read time but not offered as a save target during first-time setup.

After Setup

1. Create the directory if needed 2. Write EXTEND.md with frontmatter (see template below) 3. Confirm: "Preferences saved to [path]" 4. Continue to Step 1.2

EXTEND.md Template

---
version: 1
preferred_layout: [selected layout or null]
preferred_style: [selected style or null]
preferred_aspect: [landscape|portrait|square|null]
language: [selected language or null]
preferred_image_backend: auto
custom_styles: []
---

preferred_image_backend: auto is the baked-in default — first-time setup never asks about it. The ## Image Generation Tools rule in SKILL.md then picks the runtime-native tool (Codex imagegen, Hermes image_generate, etc.) when one is available, and falls back to installed backends like baoyu-image-gen.

Modifying Preferences Later

See the ## Changing Preferences section in SKILL.md for the canonical list of common edits (pin backend, change layout/style defaults, retrigger setup). Full schema: references/config/preferences-schema.md.

Preferences Schema

Full Schema

---
version: 1

preferred_layout: null    # any of the 21 layouts (see Layout Gallery in SKILL.md) or null
preferred_style: null     # any of the 21 styles (see Style Gallery in SKILL.md) or null
preferred_aspect: null    # landscape|portrait|square|null  (custom W:H also accepted)

language: null            # zh|en|ja|ko|null (null = auto-detect from source)

preferred_image_backend: auto   # auto|ask|<backend-id>

custom_styles:            # extra style definitions merged with the 21 built-ins
  - name: my-brand
    description: "Short description shown in Step 3 recommendations"
    prompt_fragment: "Style traits to inject into Step 5 prompt"
---

Field Reference

Backend resolution logic is documented in the ## Image Generation Tools section of SKILL.md. This doc only defines the field.

All fields in this schema are defaults only — they shape Step-3 recommendations and Step-4 defaults but never bypass Step 4 confirmation (see the ## Confirmation Policy section in SKILL.md).

Example backend ids:

Layout Options

See the Layout Gallery (21) table in SKILL.md for the canonical list. Common picks:

Style Options

See the Style Gallery (21) table in SKILL.md for the canonical list. Common picks:

Aspect Options

Custom Style Fields

Example: Minimal Preferences

---
version: 1
preferred_layout: bento-grid
preferred_style: craft-handmade
language: zh
---

preferred_image_backend is omitted above; absence is treated as auto.

Example: Full Preferences

---
version: 1

preferred_layout: dense-modules
preferred_style: morandi-journal
preferred_aspect: portrait

language: zh

preferred_image_backend: codex-imagegen

custom_styles:
  - name: my-brand
    description: "Brand-aligned warm pastel infographic"
    prompt_fragment: "Use brand pastel palette (#F2C7B6, #B6D7E8, #C8E0B4); rounded rectangles; warm hand-drawn outlines; ample whitespace."
---

bento-grid

Modular grid layout with varied cell sizes, like a bento box.

Structure

• Grid of rectangular cells
• Mixed cell sizes (1x1, 2x1, 1x2, 2x2)
• No strict symmetry required
• Hero cell for main point
• Supporting cells around it

Best For

• Multiple topic overview
• Feature highlights
• Dashboard summaries
• Portfolio displays
• Mixed content types

Visual Elements

• Clear cell boundaries
• Varied cell backgrounds
• Icons or illustrations per cell
• Consistent padding/margins
• Visual hierarchy through size

Text Placement

• Main title at top
• Cell titles within each cell
• Brief content per cell
• Minimal text, maximum visual
• CTA or summary in prominent cell

Recommended Pairings

• craft-handmade: Friendly overviews (default)
• corporate-memphis: Business summaries
• pixel-art: Retro feature grids

binary-comparison

Side-by-side comparison of two items, states, or concepts.

Structure

• Vertical divider splitting image in half
• Left side: Item A / Before / Pro
• Right side: Item B / After / Con
• Mirrored layout for easy comparison
• Clear visual distinction between sides

Variants

Best For

• Before/after transformations
• Product or option comparisons
• Pros and cons analysis
• Old vs new comparisons
• Two perspectives on a topic

Visual Elements

• Strong vertical dividing line or gradient
• Contrasting colors per side
• Matching element positions for comparison
• VS symbol or divider decoration
• Transformation arrow for before-after

Text Placement

• Main title centered at top
• Side labels (A/B, Before/After)
• Corresponding points aligned horizontally
• Summary at bottom if needed

Recommended Pairings

• corporate-memphis: Business comparisons
• bold-graphic: High-contrast dramatic comparisons
• craft-handmade: Friendly explainers

bridge

Gap-crossing structure connecting problem to solution or current to future state.

Structure

• Left side: current state/problem
• Right side: desired state/solution
• Bridge element spanning the gap
• Gap representing challenge/obstacle
• Bridge elements as steps/methods

Best For

• Problem to solution journeys
• Current vs future state
• Gap analysis
• Transformation bridges
• Strategic initiatives

Visual Elements

• Two distinct platforms/sides
• Visible gap or chasm
• Bridge structure with supports
• Icons representing each side
• Stepping stones or bridge planks

Text Placement

• Title at top
• Left label (From/Problem/Current)
• Right label (To/Solution/Future)
• Bridge elements labeled
• Gap description below

Recommended Pairings

• cartoon-hand-drawn: Friendly journeys
• corporate-memphis: Business transformations
• isometric-3d: Technical transitions

circular-flow

Cyclic process showing continuous or recurring steps.

Structure

• Circular arrangement
• Steps around the circle
• Arrows showing direction
• No clear start/end (continuous)
• Center can hold main concept

Best For

• Recurring processes
• Feedback loops
• Lifecycle stages
• Continuous improvement
• Natural cycles

Visual Elements

• Circle or ring shape
• Directional arrows
• Step nodes evenly spaced
• Icons per step
• Optional center element

Text Placement

• Title at top
• Step labels at each node
• Brief descriptions near nodes
• Center concept if applicable
• Cycle name

Recommended Pairings

• cartoon-hand-drawn: Friendly cycles
• corporate-memphis: Business processes
• subway-map: Transit-style cycles

comic-strip

Sequential narrative panels telling a story or explaining a concept.

Structure

• Multiple panels in sequence
• Left-to-right, top-to-bottom reading
• Characters or subjects in scenes
• Speech/thought bubbles
• Panel borders clearly defined

Best For

• Storytelling explanations
• User journey narratives
• Scenario illustrations
• Step sequences with context
• Before/during/after stories

Visual Elements

• Panel frames
• Speech and thought bubbles
• Sound effects (optional)
• Characters with expressions
• Scene backgrounds

Text Placement

• Title at top
• Dialogue in speech bubbles
• Narration in caption boxes
• Sound effects integrated
• Panel numbers if needed

Recommended Pairings

• graphic-novel: Dramatic narratives
• kawaii: Cute character stories
• cartoon-hand-drawn: Friendly explanations

comparison-matrix

Grid-based multi-factor comparison across multiple items.

Structure

• Table/grid layout
• Rows: items being compared
• Columns: comparison criteria
• Cells: scores, checks, or values
• Header row and column clearly marked

Best For

• Product feature comparisons
• Tool/software evaluations
• Multi-criteria decisions
• Specification sheets
• Rating comparisons

Visual Elements

• Clear grid lines or cell boundaries
• Checkmarks, X marks, or scores in cells
• Color coding for quick scanning
• Icons for criteria categories
• Highlight for recommended option

Text Placement

• Title at top
• Item names in first column
• Criteria in header row
• Brief values in cells
• Legend if using symbols

Recommended Pairings

• corporate-memphis: Business tool comparisons
• ui-wireframe: Technical feature matrices
• blueprint: Specification comparisons

dashboard

Multi-metric display with charts, numbers, and KPI indicators.

Structure

• Multiple data widgets
• Charts, graphs, numbers
• Grid or modular layout
• Key metrics prominent
• Status indicators

Best For

• KPI summaries
• Performance metrics
• Analytics overviews
• Status reports
• Data snapshots

Visual Elements

• Chart types (bar, line, pie, gauge)
• Big numbers for KPIs
• Trend arrows (up/down)
• Color-coded status (green/red)
• Clean data visualization

Text Placement

• Title at top
• Widget titles above each section
• Metric labels and values
• Units clearly shown
• Time period indicated

Recommended Pairings

• corporate-memphis: Business dashboards
• ui-wireframe: Technical dashboards
• cyberpunk-neon: Futuristic displays

dense-modules

High-density modular layout with 6-7 typed information modules packed with concrete data.

Structure

• 6-7 distinct modules per image, each serving a specific information function
• Every module contains concrete data: brand names, numbers, percentages, parameters
• Minimal whitespace—compact spacing prioritized over breathing room
• Smaller text acceptable to maximize information density
• Each module identified by coordinate label or section marker (e.g., MOD-1, SEC-A)

Module Archetypes

Variants

Best For

• Product selection guides and buying guides
• Multi-dimensional comparison content
• Data-rich educational materials
• "Avoid pitfalls" / "complete guide" formats
• Content targeting platforms like Xiaohongshu with high-density visual requirements

Visual Elements

• Module boundary markers (thick lines, dotted frames, or coordinate grids)
• Quality indicators per module (emoji faces, checkmarks, crosses, crowns)
• Data callout boxes with highlighted numbers
• Comparison arrows and progression indicators
• Warning/alert visual markers for pitfall modules
• Metadata in corners (page numbers, timestamps, small barcodes)

Text Placement

• Main title at top, prominent and impactful
• Subtitle with module count ("X大维度全面解析...")
• Module headers inside colored badges or labeled frames
• Body text compact, multiple columns within modules
• Numbers highlighted with accent colors, slightly larger than body text

Information Density Rules

• Every corner should contain useful information or metadata
• No decorative-only empty space
• Text size may be reduced to fit more content—information over font size
• Each module must have specific data points, not generic descriptions
• Balance between density and readability: dense but organized

Recommended Pairings

• pop-laboratory: Technical precision with coordinate markers and blueprint grid
• morandi-journal: Hand-drawn warmth with doodle illustrations and organic frames
• retro-pop-grid: 1970s pop art with strict grid cells and bold contrast
• retro-popup-pop: Vintage desktop popups with chunky pixel UI for retro-tech dense guides
• corporate-memphis: Clean business feel for product comparisons
• technical-schematic: Engineering precision for technical product guides

funnel

Narrowing stages showing conversion, filtering, or refinement process.

Structure

• Wide top (input/start)
• Narrow bottom (output/result)
• Horizontal layers for stages
• Progressive narrowing
• 3-6 stages typically

Best For

• Sales/marketing funnels
• Conversion processes
• Filtering/selection
• Recruitment pipelines
• Decision processes

Visual Elements

• Funnel shape clearly defined
• Distinct colors per stage
• Width indicates volume/quantity
• Stage icons or symbols
• Numbers/percentages per stage

Text Placement

• Title at top
• Stage names inside or beside
• Metrics/numbers per stage
• Input label at top
• Output label at bottom

Recommended Pairings

• corporate-memphis: Marketing funnels
• isometric-3d: Technical pipelines
• cartoon-hand-drawn: Educational funnels

hierarchical-layers

Nested layers showing levels of importance, influence, or proximity.

Structure

• Multiple layers from core to periphery
• Core/top: most important/central
• Outer/bottom: decreasing importance
• 3-7 levels typically
• Clear boundaries between levels

Variants

Best For

• Maslow's hierarchy style concepts
• Priority and importance levels
• Spheres of influence
• Organizational structures
• Stakeholder analysis

Visual Elements

• Distinct color per level
• Icons or illustrations per tier
• Size indicates importance/quantity
• Labels inside or beside layers
• Decorative apex/center element

Text Placement

• Title at top or side
• Level names inside each tier
• Brief descriptions outside
• Quantities or percentages if relevant
• Legend for color meanings

Recommended Pairings

• craft-handmade: Playful layered concepts
• corporate-memphis: Business hierarchies
• technical-schematic: Technical 3D pyramids

hub-spoke

Central concept with radiating connections to related items.

Structure

• Central hub (main concept)
• Spokes radiating outward
• Nodes at spoke ends (related concepts)
• Even or weighted distribution
• Optional secondary connections

Best For

• Central theme with components
• Product features around core
• Team roles around project
• Ecosystem mapping
• Mind maps

Visual Elements

• Prominent central hub
• Clear spoke lines
• Consistent node styling
• Icons representing each spoke item
• Optional grouping colors

Text Placement

• Title at top
• Core concept in center hub
• Spoke item labels at nodes
• Brief descriptions near nodes
• Connection labels on spokes if needed

Recommended Pairings

• cartoon-hand-drawn: Friendly concept maps
• corporate-memphis: Business ecosystems
• subway-map: Network-style connections

iceberg

Surface vs hidden depths, visible vs underlying factors.

Structure

• Waterline dividing visible/hidden
• Tip above water (obvious/surface)
• Larger mass below (hidden/deep)
• Proportional to emphasize hidden depth
• Optional layers within underwater section

Best For

• Surface vs root causes
• Visible vs invisible work
• Symptoms vs underlying issues
• Public vs private aspects
• Known vs unknown factors

Visual Elements

• Clear water/surface line
• Above: smaller, brighter
• Below: larger, darker/deeper
• Wave or water texture
• Gradient showing depth

Text Placement

• Title at top
• Surface items above waterline
• Hidden items below, larger
• Waterline label optional
• Depth indicators for layers

Recommended Pairings

• cartoon-hand-drawn: Friendly metaphor
• storybook-watercolor: Artistic depth
• graphic-novel: Dramatic revelation

isometric-map

3D-style spatial layout showing locations, relationships, or journey through space.

Structure

• Isometric 3D perspective
• Locations as buildings/landmarks
• Paths connecting locations
• Spatial relationships visible
• Bird's eye view angle

Best For

• Office/campus layouts
• City/ecosystem maps
• User journey maps
• System architecture
• Process landscapes

Visual Elements

• Consistent isometric angle (30°)
• 3D buildings or objects
• Pathways and roads
• Labels floating above
• Mini scenes at locations

Text Placement

• Title at top corner
• Location labels above objects
• Path labels along routes
• Legend for symbols
• Scale indicator if relevant

Recommended Pairings

• isometric-3d: Clean technical maps
• pixel-art: Retro game-style maps
• lego-brick: Playful location maps

jigsaw

Interlocking puzzle pieces showing how parts fit together.

Structure

• Puzzle pieces that interlock
• Each piece represents a component
• Connections show relationships
• Can be assembled or exploded view
• Missing piece highlights gaps

Best For

• Component relationships
• Team/skill fit
• Strategy pieces
• Integration concepts
• Completeness assessments

Visual Elements

• Classic puzzle piece shapes
• Distinct colors per piece
• Interlocking edges visible
• Icons or labels per piece
• Optional missing piece

Text Placement

• Title at top
• Piece labels inside or beside
• Connection descriptions
• Missing piece explanation
• Assembly context

Recommended Pairings

• cartoon-hand-drawn: Friendly integration concepts
• paper-cutout: Tactile puzzle feel
• corporate-memphis: Business strategy pieces

linear-progression

Sequential progression showing steps, timeline, or chronological events.

Structure

• Linear arrangement (horizontal or vertical)
• Nodes/markers at key points
• Connecting line or path between nodes
• Clear start and end points
• Directional flow indicators

Variants

Best For

• Step-by-step tutorials and how-tos
• Historical timelines and evolution
• Project milestones and roadmaps
• Workflow documentation
• Onboarding processes

Visual Elements

• Numbered steps or date markers
• Arrows or connectors showing direction
• Icons representing each step/event
• Consistent node spacing
• Progress indicators optional

Text Placement

• Title at top
• Step/event titles at each node
• Brief descriptions below nodes
• Dates or numbers clearly visible

Recommended Pairings

• craft-handmade: Friendly tutorials and timelines
• ikea-manual: Clean assembly instructions
• corporate-memphis: Business process flows
• aged-academia: Historical discoveries

periodic-table

Grid of categorized elements with consistent cell formatting.

Structure

• Rectangular grid
• Each cell is one element
• Color-coded categories
• Consistent cell format
• Optional grouping gaps

Best For

• Categorized collections
• Tool/resource catalogs
• Skill matrices
• Element collections
• Reference guides

Visual Elements

• Uniform cell sizes
• Category colors
• Symbol/abbreviation prominent
• Small icon per cell
• Category legend

Text Placement

• Title at top
• Cell: symbol, name, brief info
• Category names in legend
• Optional row/column headers
• Footnotes for special cases

Recommended Pairings

• pop-art: Vibrant element grids
• pixel-art: Retro collection displays
• corporate-memphis: Business tool catalogs

story-mountain

Plot structure visualization showing rising action, climax, and resolution.

Structure

• Mountain/arc shape
• Rising slope (build-up)
• Peak (climax)
• Falling slope (resolution)
• Start and end at base level

Best For

• Narrative structures
• Project lifecycles
• Tension/release patterns
• Emotional journeys
• Campaign arcs

Visual Elements

• Mountain or arc curve
• Points along the path
• Climax visually emphasized
• Slope steepness meaningful
• Base camps or milestones

Text Placement

• Title at top
• Stage labels along path
• Climax prominently labeled
• Brief descriptions at points
• Start/end clearly marked

Recommended Pairings

• storybook-watercolor: Narrative journeys
• cartoon-hand-drawn: Educational plot diagrams
• graphic-novel: Dramatic story arcs

structural-breakdown

Internal structure visualization with labeled parts or layers.

Structure

• Central subject (object, system, body)
• Parts or layers clearly shown
• Labels with callout lines
• Exploded or cutaway view
• Optional zoomed detail sections

Variants

Best For

• Product part breakdowns
• Anatomy explanations
• System components
• Device teardowns
• Material composition

Visual Elements

• Main subject clearly rendered
• Callout lines with dots/arrows
• Label boxes at endpoints
• Numbered parts optionally
• Layer boundaries or separation

Text Placement

• Title at top
• Part/layer labels at callouts
• Brief descriptions in boxes
• Legend for numbered systems
• Depth/thickness if relevant

Recommended Pairings

• technical-schematic: Technical schematics
• aged-academia: Classic anatomical style
• craft-handmade: Friendly breakdowns

tree-branching

Hierarchical structure branching from root to leaves, showing categories and subcategories.

Structure

• Root/trunk at top or left
• Branches splitting into sub-branches
• Leaves as terminal nodes
• Clear parent-child relationships
• Balanced or organic branching

Best For

• Taxonomies and classifications
• Decision trees
• Organizational charts
• File/folder structures
• Family trees

Visual Elements

• Connecting lines showing relationships
• Nodes at branch points
• Icons or labels at each node
• Color coding by branch
• Visual weight decreasing toward leaves

Text Placement

• Title at top
• Root concept prominently labeled
• Branch and leaf labels
• Optional descriptions at key nodes
• Legend for categories

Recommended Pairings

• cartoon-hand-drawn: Friendly taxonomies
• da-vinci-notebook: Scientific classifications
• origami: Geometric tree structures

venn-diagram

Overlapping circles showing relationships, commonalities, and differences.

Structure

• 2-3 overlapping circles
• Each circle is a category/concept
• Overlaps show shared elements
• Center shows common to all
• Unique areas for exclusives

Best For

• Concept relationships
• Skill overlaps
• Market segments
• Comparative analysis
• Finding common ground

Visual Elements

• Translucent circle fills
• Clear overlap regions
• Distinct colors per circle
• Icons in regions
• Boundary labels

Text Placement

• Title at top
• Circle labels outside or on edge
• Items in appropriate regions
• Overlap region labels
• Legend if needed

Recommended Pairings

• cartoon-hand-drawn: Friendly concept overlaps
• corporate-memphis: Business segment analysis
• pop-art: High-contrast comparisons

winding-roadmap

Curved path showing journey with milestones and checkpoints.

Structure

• S-curve or winding path
• Milestones along the path
• Start and destination points
• Side elements (obstacles, helpers)
• Progress indicators

Best For

• Project roadmaps
• Career paths
• Customer journeys
• Learning paths
• Strategy timelines

Visual Elements

• Curving road or river
• Milestone markers/flags
• Scene elements along path
• Vehicle/character on journey
• Destination landmark

Text Placement

• Title at top
• Milestone labels at each point
• Path section names
• Destination description
• Optional timeline indicators

Recommended Pairings

• storybook-watercolor: Whimsical journeys
• cartoon-hand-drawn: Friendly roadmaps
• isometric-3d: Technical project paths

Structured Content Template

Template for generating structured infographic content that informs the visual designer.

Purpose

This document bridges content analysis and visual design:

• Transforms source material into designer-ready format
• Organizes learning objectives into visual sections
• Preserves all source data verbatim
• Separates content from design instructions

Instructional Design Process

Phase 1: High-Level Outline

1. Title: Capture the essence in a compelling headline 2. Overview: Brief description (1-2 sentences) 3. Learning Objectives: List what the viewer will understand

Phase 2: Section Development

For each learning objective:

1. Key Concept: One-sentence summary of the section 2. Content: Points extracted verbatim from source 3. Visual Element: What should be shown visually 4. Text Labels: Exact text for headlines, subheads, labels

Phase 3: Data Integrity Check

Verify all source data is:

• Copied exactly (no paraphrasing)
• Attributed correctly (for quotes)
• Formatted consistently

Critical Rules

Structured Content Format

# [Infographic Title]

## Overview
[Brief description of what this infographic conveys - 1-2 sentences]

## Learning Objectives
The viewer will understand:
1. [Primary objective]
2. [Secondary objective]
3. [Tertiary objective if applicable]

---

## Section 1: [Section Title]

**Key Concept**: [One-sentence summary of this section]

**Content**:
- [Point 1 - verbatim from source]
- [Point 2 - verbatim from source]
- [Point 3 - verbatim from source]

**Visual Element**: [Description of what to show visually]
- Type: [icon/chart/illustration/diagram/photo]
- Subject: [what it depicts]
- Treatment: [how it should be presented]

**Text Labels**:
- Headline: "[Exact text for headline]"
- Subhead: "[Exact text for subhead]"
- Labels: "[Label 1]", "[Label 2]", "[Label 3]"

---

## Section 2: [Section Title]

**Key Concept**: [One-sentence summary]

**Content**:
- [Point 1]
- [Point 2]

**Visual Element**: [Description]

**Text Labels**:
- Headline: "[text]"
- Labels: "[Label 1]", "[Label 2]"

---

[Continue for each section...]

---

## Data Points (Verbatim)

All statistics, numbers, and quotes exactly as they appear in source:

### Statistics
- "[Exact statistic 1]"
- "[Exact statistic 2]"
- "[Exact statistic 3]"

### Quotes
- "[Exact quote]" — [Attribution]

### Key Terms
- **[Term 1]**: [Definition from source]
- **[Term 2]**: [Definition from source]

---

## Design Instructions

Extracted from user's steering prompt:

### Style Preferences
- [Any color preferences]
- [Any mood/aesthetic preferences]
- [Any artistic style preferences]

### Layout Preferences
- [Any structure preferences]
- [Any organization preferences]

### Other Requirements
- [Any other visual requirements from user]
- [Target platform if specified]
- [Brand guidelines if any]

Section Types by Content

For Process/Steps

## Section N: Step N - [Step Title]

**Key Concept**: [What this step accomplishes]

**Content**:
- Action: [What to do]
- Details: [How to do it]
- Note: [Important consideration]

**Visual Element**:
- Type: numbered step icon
- Subject: [visual representing the action]
- Arrow: leads to next step

**Text Labels**:
- Headline: "Step N: [Title]"
- Action: "[Imperative verb + object]"

For Comparison

## Section N: [Item A] vs [Item B]

**Key Concept**: [What distinguishes them]

**Content**:
| Aspect | [Item A] | [Item B] |
|--------|----------|----------|
| [Factor 1] | [Value] | [Value] |
| [Factor 2] | [Value] | [Value] |

**Visual Element**:
- Type: split comparison
- Left: [Item A representation]
- Right: [Item B representation]

**Text Labels**:
- Headline: "[Item A] vs [Item B]"
- Left label: "[Item A name]"
- Right label: "[Item B name]"

For Hierarchy

## Section N: [Level Name]

**Key Concept**: [What this level represents]

**Content**:
- Position: [Top/Middle/Bottom]
- Priority: [Importance level]
- Contains: [Elements at this level]

**Visual Element**:
- Type: layer/tier
- Size: [relative to other levels]
- Position: [where in hierarchy]

**Text Labels**:
- Level title: "[Name]"
- Description: "[Brief description]"

For Data/Statistics

## Section N: [Metric Name]

**Key Concept**: [What this data shows]

**Content**:
- Value: [Exact number/percentage]
- Context: [What it means]
- Comparison: [Benchmark if any]

**Visual Element**:
- Type: [chart/number highlight/gauge]
- Emphasis: [how to draw attention]

**Text Labels**:
- Main number: "[Exact value]"
- Label: "[Metric name]"
- Context: "[Brief context]"

Quality Checklist

Before finalizing structured content:

• [ ] Title captures the main message
• [ ] Learning objectives are clear and measurable
• [ ] Each section maps to an objective
• [ ] All content is verbatim from source
• [ ] Visual elements are clearly described
• [ ] Text labels are specified exactly
• [ ] Data points are collected and verified
• [ ] Design instructions are separated
• [ ] No new information has been added

aged-academia

Historical scientific illustration with aged paper aesthetic.

Color Palette

• Primary: Sepia brown (#704214), aged ink, muted earth tones
• Background: Parchment (#F4E4BC), yellowed paper texture
• Accents: Faded red annotations, iron gall ink spots

Variants

Visual Elements

• Aged paper texture overlay
• Detailed cross-hatching and line work
• Scientific illustration precision
• Study notes and annotations
• Specimen plate or sketch aesthetic
• Numbered diagram elements

Typography

• Handwritten cursive or serif fonts
• Scientific annotations
• Small caps for labels
• Italics for scientific names

Best For

Scientific education, biology topics, historical explanations, inventions, nature documentation

bold-graphic

High-contrast comic style with bold outlines and dramatic visuals.

Color Palette

• Primary: Bold primaries - red, yellow, blue, black
• Background: White, halftone patterns, dramatic shadows
• Accents: Spot colors, neon highlights

Variants

Visual Elements

• Bold black outlines
• High contrast compositions
• Halftone dot patterns
• Comic panel borders optional
• Action lines and motion
• Speech bubbles and sound effects

Typography

• Comic book lettering
• Impact fonts for emphasis
• POW/BANG effects for pop-art
• Caption boxes for narrative

Best For

Attention-grabbing content, dramatic narratives, pop culture, marketing, high-energy presentations

chalkboard

Black chalkboard background with colorful chalk drawing style

Design Aesthetic

Classic classroom chalkboard aesthetic with hand-drawn chalk illustrations. Nostalgic educational feel with imperfect, sketchy lines that capture the warmth of traditional teaching. Colorful chalk creates visual hierarchy while maintaining the authentic chalkboard experience.

Background

• Color: Chalkboard Black (#1A1A1A) or Dark Green-Black (#1C2B1C)
• Texture: Realistic chalkboard texture with subtle scratches, dust particles, and faint eraser marks

Typography

Hand-drawn chalk lettering style with visible chalk texture. Imperfect baseline adds authenticity. White or bright colored chalk for emphasis.

Color Palette

Visual Elements

• Hand-drawn chalk illustrations with sketchy, imperfect lines
• Chalk dust effects around text and key elements
• Doodles: stars, arrows, underlines, circles, checkmarks
• Mathematical formulas and simple diagrams
• Eraser smudges and chalk residue textures
• Wooden frame border optional
• Stick figures and simple icons
• Connection lines with hand-drawn feel

Style Rules

Do

• Maintain authentic chalk texture on all elements
• Use imperfect, hand-drawn quality throughout
• Add subtle chalk dust and smudge effects
• Create visual hierarchy with color variety
• Include playful doodles and annotations

Don't

• Use perfect geometric shapes
• Create clean digital-looking lines
• Add photorealistic elements
• Use gradients or glossy effects

Best For

Educational content, tutorials, classroom themes, teaching materials, workshops, informal learning sessions, knowledge sharing

claymation

3D clay figure aesthetic with stop-motion charm

Color Palette

• Primary: Saturated clay colors - bright but slightly muted
• Background: Neutral studio backdrop, soft gradients
• Accents: Complementary clay colors, shiny highlights

Visual Elements

• Clay/plasticine texture on all objects
• Fingerprint marks and imperfections
• Rounded, sculpted forms
• Soft shadows
• Stop-motion staging
• Miniature set aesthetic

Typography

• Extruded clay letters
• Dimensional, rounded text
• Playful and chunky
• Embedded in clay scenes

Best For

Playful explanations, children's content, stop-motion narratives, friendly processes

corporate-memphis

Flat vector people with vibrant geometric fills

Color Palette

• Primary: Bright, saturated - purple, orange, teal, yellow
• Background: White or light pastels
• Accents: Gradient fills, geometric patterns

Visual Elements

• Flat vector illustration
• Disproportionate human figures
• Abstract body shapes
• Floating geometric elements
• No outlines, solid fills
• Plant and object accents

Typography

• Clean sans-serif
• Bold headings
• Professional but friendly
• Minimal decoration

Best For

Business presentations, tech products, marketing materials, corporate training

craft-handmade (DEFAULT)

Hand-drawn and paper craft aesthetic with warm, organic feel.

Color Palette

• Primary: Warm pastels, soft saturated colors, craft paper tones
• Background: Light cream (#FFF8F0), textured paper (#F5F0E6)
• Accents: Bold highlights, construction paper colors

Variants

Visual Elements

• Hand-drawn or cut-paper quality
• Organic, slightly imperfect shapes
• Layered depth with shadows (paper variant)
• Simple cartoon elements and icons
• Character illustrations (people, personalities in cartoon form)
• Ample whitespace, clean composition
• Keywords and core concepts highlighted
• Strictly hand-drawn—no realistic or photographic elements

Style Enforcement

• All imagery must maintain cartoon/illustrated aesthetic
• Replace real photos or realistic figures with hand-drawn equivalents
• Maintain consistent line weight and illustration style throughout

Typography

• Hand-drawn or casual font style
• Clear, readable labels
• Keywords emphasized with larger/bolder text
• Cut-out letter style for paper variant

Best For

Educational content, general explanations, friendly infographics, children's content, playful hierarchies

cyberpunk-neon

Neon glow on dark backgrounds, futuristic aesthetic

Color Palette

• Primary: Neon pink (#FF00FF), cyan (#00FFFF), electric blue
• Background: Deep black (#0A0A0A), dark purple gradients
• Accents: Neon glow effects, chrome reflections

Visual Elements

• Glowing neon outlines
• Dark atmospheric backgrounds
• Digital glitch effects
• Circuit patterns
• Holographic elements
• Rain and reflections

Typography

• Glowing neon text
• Digital/tech fonts
• Flickering effects
• Outlined glow letters

Best For

Tech futures, gaming content, digital culture, futuristic concepts, night aesthetics

hand-drawn-edu

Hand-drawn educational infographic with macaron pastel color blocks on warm cream paper texture.

Color Palette

• Background: Warm cream (#F5F0E8) with subtle paper grain texture
• Primary text: Deep charcoal (#2D2D2D) for headlines, outlines
• Macaron Blue: #A8D8EA for cool-toned information zones
• Macaron Mint: #B5E5CF for growth/positive zones
• Macaron Lavender: #D5C6E0 for abstract/concept zones
• Macaron Peach: #FFD5C2 for warm-toned zones
• Accent: Coral Red (#E8655A) for key data, warnings, emphasis
• Muted annotations: Warm gray (#6B6B6B) for secondary labels

Visual Elements

• Macaron pastel rounded cards as distinct information zones
• Hand-drawn wavy connection lines and arrows with small text labels
• Simple stick-figure characters and cartoon icons to humanize concepts
• Doodle decorations: small stars, underlines, spirals, sparkles
• Color fills don't completely fill outlines — preserve casual hand-drawn feel
• Dashed borders for secondary or contained zones
• Small icon doodles (clipboard, lock, checkmark, lightbulb) to reinforce concepts
• Bold centered quote or takeaway at the bottom
• Slight hand-drawn wobble on all lines and shapes

Variants

Typography

• Main title: Bold hand-drawn lettering with organic strokes, large confident letterforms with slight wobble
• Section headers: Hand-lettered text on or inside macaron color blocks
• Body text: Clear handwritten print style, legible but not mechanical
• Annotations: Warm gray (#6B6B6B), smaller, neat handwritten labels
• Keywords: Bold emphasis within body text

Style Enforcement

• All lines must have slight hand-drawn wobble — no perfect geometry
• Each information zone uses a distinct macaron color block
• Maintain consistent wobble quality across all shapes and lines
• Include at least one simple cartoon character or stick figure
• Generous white space between zones — each zone should breathe
• Maximum 4 macaron colors per infographic

Avoid

• Perfect geometric shapes or straight lines
• Photorealistic elements or stock illustration style
• Pure white backgrounds
• Flat vector icons or digital-precision graphics
• Overcrowded layouts — let zones breathe
• Corporate or clinical aesthetic

Best For

Educational diagrams, process explainers, concept maps, knowledge summaries, tutorial walkthroughs, onboarding visuals

ikea-manual

Minimal line art assembly instruction style

Color Palette

• Primary: Black lines, minimal fills
• Background: White or cream paper
• Accents: Red for warnings, blue for highlights

Visual Elements

• Simple line drawings
• Numbered step sequences
• Arrow indicators
• Exploded assembly views
• Wordless communication
• Stick figures for scale

Typography

• Minimal text
• Step numbers prominent
• Universal symbols
• Simple sans-serif when needed

Best For

Step-by-step instructions, assembly guides, how-to content, universal communication

kawaii

Japanese cute style with big eyes and pastel colors

Color Palette

• Primary: Soft pastels - pink (#FFB6C1), mint (#98D8C8), lavender (#E6E6FA)
• Background: Light pink or cream, sparkle overlays
• Accents: Bright pops, star and heart shapes

Visual Elements

• Big sparkly eyes on characters
• Rounded, soft shapes
• Blushing cheeks
• Sparkles and stars scattered
• Cute animal characters
• Chibi proportions

Typography

• Rounded, bubbly fonts
• Cute decorations on letters
• Hearts and stars in text
• Soft, friendly appearance

Best For

Cute tutorials, children's education, lifestyle content, character-driven explanations

knolling

Organized flat-lay with top-down arrangement

Color Palette

• Primary: Object's natural colors
• Background: Solid color - black, white, or colored surface
• Accents: Shadows, subtle highlights

Visual Elements

• Top-down camera angle
• Objects arranged at 90° angles
• Equal spacing between items
• Clean organization
• Symmetry and order
• No overlapping items

Typography

• Clean labels
• Positioned outside objects
• Connecting lines to items
• Minimal, catalog-style

Best For

Product collections, tool inventories, gear layouts, organized overviews

lego-brick

Toy brick construction with playful aesthetic

Color Palette

• Primary: Classic LEGO colors - red, blue, yellow, green, white
• Background: Light gray baseplate or white
• Accents: Bright primary pops, shiny studs

Visual Elements

• Visible brick studs
• Modular construction
• Minifigure characters
• Building instruction style
• Stackable elements
• Plastic sheen

Typography

• Blocky, bold fonts
• LEGO instruction style
• Step numbers
• Playful appearance

Best For

Building concepts, modular systems, playful education, children's content

morandi-journal

Hand-drawn doodle illustration with warm Morandi color tones and cozy bullet journal aesthetic.

Color Palette

• Background: Warm cream/beige with subtle paper texture (#F5F0E6)
• Primary: Muted teal/sage green (#7BA3A8) for headers and frames
• Secondary: Warm terracotta/orange (#D4956A) for highlights and numbers
• Line art: Dark charcoal brown (#4A4540)
• Soft highlights: Pale yellow (#F5E6C8)

Visual Elements

• Hand-drawn doodle illustrations with organic, slightly imperfect ink lines
• Washi tape strip decorations (diagonal stripes pattern, beige and brown)
• Rounded card containers for brand/option items
• Hand-drawn rulers, scales, and progress bars with emoji quality indicators
• Smiley/frowny faces as quality markers (😊✓ 😐 ☹️✗)
• Dotted line frames around sections
• Connecting arrows and dotted lines between modules
• Corner decorations: tiny houses, stars, sparkles, clouds
• Wavy line dividers between sections
• Callout bubbles for tips
• Magnifying glass icons for identification tips
• Thumbs up/down icons (hand-drawn style)

Variants

Typography

• Main title: Bold hand-lettered calligraphy style with decorative flourishes
• Module headers: Clean handwritten text in white on dark teal rounded badge (#6B9080)
• Body text: Neat handwritten print style, easy to read
• Numbers: Highlighted in terracotta (#D4956A), slightly larger than body

Style Enforcement

• All imagery must maintain hand-drawn/doodle aesthetic—no digital precision
• Organic, slightly imperfect shapes throughout
• Sketch-like quality with visible line weight variations
• Warm and cozy journal feel, not clinical or corporate

Avoid

• Flat vector icons or emoji
• Clean geometric shapes
• Stock illustration style
• Strict grid layout
• Pure white background
• Digital/corporate look

Best For

Product selection guides, lifestyle content, educational overviews, consumer-facing comparison content, Xiaohongshu-style posts

origami

Folded paper forms with geometric precision

Color Palette

• Primary: Solid origami paper colors - red, blue, green, gold
• Background: White or soft gray, subtle shadows
• Accents: Paper fold highlights, crisp shadows

Visual Elements

• Geometric folded shapes
• Visible fold lines
• Cast shadows showing depth
• Paper texture
• Angular, faceted forms
• Low-poly aesthetic

Typography

• Clean geometric fonts
• Angular letterforms
• Folded paper text effect
• Minimal, precise labels

Best For

Geometric concepts, transformation topics, Japanese themes, abstract representations

pixel-art

Retro 8-bit gaming aesthetic

Color Palette

• Primary: Limited palette - NES/SNES colors
• Background: Black or dark blue, scanlines optional
• Accents: Bright pixel highlights, CRT glow

Visual Elements

• Visible pixel grid
• Limited color count per sprite
• 8-bit or 16-bit style
• Retro game UI elements
• Pixel-perfect edges
• Dithering for gradients

Typography

• Pixel fonts
• Blocky letterforms
• Game UI style text
• Score/stat display style

Best For

Gaming topics, nostalgia content, developer audiences, retro tech themes

pop-laboratory

Lab manual precision meets pop art color impact—coordinate systems, technical diagrams, and fluorescent accents on blueprint grid.

Color Palette

• Background: Professional grayish-white with faint blueprint grid texture (#F2F2F2)
• Primary: Muted teal/sage green (#B8D8BE) for major functional blocks and data zones
• High-alert accent: Vibrant fluorescent pink (#E91E63) strictly for warnings, critical data, or "winner" highlights
• Marker highlights: Vivid lemon yellow (#FFF200) as translucent highlighter effect for keywords
• Line art: Ultra-fine charcoal brown (#2D2926) for technical grids, coordinates, and hairlines

Visual Elements

• Coordinate-style labels on every module (e.g., R-20, G-02, SEC-08)
• Technical diagrams: exploded views, cross-sections with anchor points, architectural skeletal lines
• Vertical/horizontal rulers with precise markers (0.5mm, 1.8mm, 45°)
• "Marker-over-print" effect: color blocks slightly offset from text, postmodern print feel
• Cross-hair targets, mathematical symbols (Σ, Δ, ∞), directional arrows (X/Y axis)
• Microscopic detail annotations alongside macroscopic bold headers
• Corner metadata: tiny barcodes, timestamps, technical parameters
• High contrast between massive bold headers and tiny 8pt-style annotations

Typography

• Headers: Bold brutalist characters, high visual impact
• Body: Professional sans-serif or crisp technical print
• Numbers: Large, highlighted with yellow or blue to stand out
• Annotations: Ultra-crisp, small technical labels

Style Enforcement

• Strictly systematic color usage: only teal, pink, yellow, charcoal—no rainbow palette
• Sufficient fine grid lines and coordinate annotations throughout
• Maintain tension between large impactful headers and small precise parameters
• Lab manual aesthetic: mix of microscopic details and macroscopic data

Avoid

• Cute or cartoonish doodles
• Soft pastels or generic textures
• Empty white space
• Flat vector stock icons
• Organic or hand-drawn imperfections

Best For

Technical product guides, specification comparisons, precision-focused data visualization, engineering-adjacent content

retro-pop-grid

1970s retro pop art with strict Swiss international grid, thick black outlines, and flat color blocks.

Color Palette

• Background: Warm vintage cream/beige (#F5F0E6)
• Flat accents: Salmon pink, sky blue, mustard yellow, mint green—all muted retro tones
• Contrast blocks: Solid pure black (#000000) and solid pure white (#FFFFFF) used strategically for extreme contrast
• Line art and outlines: Solid thick black

Visual Elements

• Uniform thick black outlines on all illustrations, text boxes, and grid dividers
• Pure 2D flat vector aesthetic with subtle screen print texture
• Strict Swiss international grid: poster divided into square and rectangular cells by thick black lines
• Black-background cells with white text for warnings or key categories (inverted contrast)
• Geometric fill patterns in empty cells: checkerboards, diagonal lines, dots
• Flat abstract symbols, warning signs, keyholes, stars, arrows
• Vintage comic-style smiley/frowny faces for quality indicators
• Colored cells used for breathing room—some with minimal/no content

Typography

• Headers: Bold brutalist or retro thick display fonts, high legibility
• Body: Clean sans-serif, structured typographic alignment
• Decorative English text acceptable for stylistic labels ("WARNING", "INFO", "BEST")
• All content text in specified language

Style Enforcement

• Absolutely no gradients, shading, drop shadows, or 3D effects
• Everything anchored in grid cells—no floating or unorganized elements
• Maintain 1970s retro pop art and underground comic illustration feel
• Visual density balanced with rhythmic grid—some cells intentionally sparse for contrast

Avoid

• 3D rendering, realistic details, gradients, soft shadows
• Soft, thin, or sketch-like pencil lines
• Free-flowing, unorganized, or floating layouts (everything must be grid-anchored)
• Pure white background canvas
• Organic or hand-drawn imperfections

Best For

Trendy product guides, design-conscious content, visually striking comparisons, content targeting design-savvy audiences, bold social media posts

retro-popup-pop

Retro pixel popup × pop-art collage — content rendered as a stack of 80/90s desktop dialog windows with thick black outlines, flat color fills, and bright cyan or vintage cream backgrounds.

Color Palette

• Background: Bright cyan (#12B8DE) primary canvas, vintage cream (#F5F0E6) alternate
• Window fills: Vintage cream (#F5F0E6) and pure white (#FFFFFF)
• Primary text and outlines: Pure black (#000000)
• Reverse text: Pure white on solid black title bars
• Accent fills (small areas only): Salmon pink, sky blue, mustard yellow, mint green — muted retro tones

Visual Elements

• 80s/90s desktop popup windows with title bars, close buttons (×), and chunky borders
• Multiple windows tiled or lightly overlapping with offset solid-black drop shadows for depth
• ERROR / ALERT / WARNING dialogs to highlight misconceptions, common pitfalls, risks
• File-window vignettes labeled with retro filenames (PROBLEMS.EXE, METHOD.PNG, BURNOUT.PSD, FOCUS_SCAN, SYSTEM_ALERT, IDEAS_MISSING)
• Progress bars for completion, difficulty, conversion rate, or trend
• Pixel-style chunky icons: folders, magnifiers, gears, exclamation marks, floppy disks, hourglasses
• Action buttons with thick black borders and short pop-style copy: OK, CANCEL, FIX IT, SCAN, PLAY, RETRY, SAVE
• Comparison data rendered as windowed lists or small tabular dialogs
• Uniform thick black outlines on every window, button, icon, and divider
• Pure 2D flat color fills throughout — no gradients, no glow, no glass

Typography

• Headers: Pixel / dot-matrix / chunky bitmap display fonts, large and high-contrast
• Body: Retro monospace or system-style sans-serif, high legibility
• Title bars: Reverse white on solid black, all-caps preferred
• Decorative all-caps English allowed for filenames, status strings, button labels (PROBLEMS.EXE, OK, CANCEL); body content text remains in the confirmed output language

Style Enforcement

• Every information chunk must live inside a window, dialog, button, or progress bar — no floating elements
• Uniform thick black outlines everywhere; offset solid-black drop shadows for stacked-window depth
• Limit accent palette to ~4 colors per composition; let cyan or cream dominate the canvas
• Maintain low-fi pixel/popup feel; humorous popup copy welcome, polished modern UI prohibited

Avoid

• Modern UI styles: glassmorphism, neumorphism, soft shadows, blurs, gradients
• 3D rendering, photorealism, ray-traced shadows
• Hand-drawn wobble, watercolor washes, or sketch textures
• Smooth anti-aliased curves on icons (prefer chunky pixel/stair-step edges)
• Pure black backgrounds — keep cyan or cream as the canvas

Best For

High-density "干货" knowledge guides, common-pitfall and debunking posts, knowledge-pop content for design-savvy or developer audiences, Xiaohongshu-style retro-tech posts, dense-modules portrait infographics.

storybook-watercolor

Soft hand-painted illustration with whimsical charm

Color Palette

• Primary: Soft watercolor washes - muted blues, greens, warm earth
• Background: Watercolor paper texture, white or cream
• Accents: Deeper pigment pools, splatter effects

Visual Elements

• Visible brushstrokes
• Soft color bleeds and gradients
• White space as design element
• Delicate line work over washes
• Natural, organic shapes
• Dreamy, atmospheric quality

Typography

• Elegant hand-lettering
• Watercolor-style text
• Flowing, organic letterforms
• Integrated with illustrations

Best For

Storytelling, emotional journeys, nature topics, children's education, artistic presentations

subway-map

Transit diagram style with colored lines and stations

Color Palette

• Primary: Transit line colors - red, blue, green, yellow, orange
• Background: White or light gray
• Accents: Station dots, interchange markers

Visual Elements

• Colored route lines
• 45° and 90° angles only
• Station circle markers
• Interchange symbols
• Simplified geography
• Line thickness hierarchy

Typography

• Clean sans-serif
• Station name labels
• Line number/name badges
• Horizontal or angled text

Best For

Journey maps, process flows, network diagrams, route explanations

technical-schematic

Technical diagrams with engineering precision and clean geometry.

Color Palette

• Primary: Blues (#2563EB), teals, grays, white lines
• Background: Deep blue (#1E3A5F), white, or light gray with grid
• Accents: Amber highlights (#F59E0B), cyan callouts

Variants

Visual Elements

• Geometric precision throughout
• Grid pattern or isometric angle
• Dimension lines and measurements
• Technical symbols and annotations
• Clean vector shapes
• Consistent stroke weights

Typography

• Technical stencil or clean sans-serif
• All-caps labels
• Measurement annotations
• Floating labels for isometric

Best For

Technical architecture, system diagrams, engineering specs, product breakdowns, data visualization

ui-wireframe

Grayscale interface mockup style

Color Palette

• Primary: Grays - light (#E5E5E5), medium (#9CA3AF), dark (#374151)
• Background: White (#FFFFFF), light gray
• Accents: Blue for interactive (#3B82F6), red for emphasis

Visual Elements

• Wireframe boxes and placeholders
• X marks for image placeholders
• Simple line icons
• Grid-based layout
• Annotation callouts
• Redline specifications

Typography

• System fonts
• Placeholder "Lorem ipsum"
• UI label style
• Sans-serif throughout

Best For

Product designs, UI explanations, app concepts, user flow diagrams