Effect preview

Turn the topic, viewpoint, article, process, or system structure given by the user into a whiteboard hand-drawn explainer diagram that looks like it was photographed in an office meeting room. The focus is "real whiteboard photographic feel + on-site Marker hand-drawing + clear explanation," rather than a clean vector poster, PPT template, or commercial illustration.
Top-level conventions
- Default aspect ratio:
16:9 - Default language: primarily Chinese, with a small amount of mixed Chinese and English allowed
- Default art style: real office whiteboard photographic feel + thick Marker hand-drawn explanation
- Default output: a complete Chinese prompt that can be used directly for image models
- Image generation tool: when the user requests "draw one / generate an image / directly output an image / draw it for me / start drawing," organize the final prompt and then call
imagegen/image_gen - Tool boundaries: this skill is only responsible for the real office whiteboard style; when generating images, do not call other illustration-type skills to rewrite the style
Applicable scenarios
Prioritize for:
- Whiteboard hand-drawn explainer diagrams, office whiteboard diagrams, meeting room whiteboard diagrams
- Startup retrospectives, project retrospectives, technical solution explanations, Agent / system / process breakdowns
Problem → Analysis → Solution、Before → Process → Result, pain point → diagnosis → solution- Need simple sketch symbols such as people, robots / Agents, computers, documents, clocks, gears, magnifying glasses, warnings, check marks, and charts to help tell the story
- The user provides long text and wants it compressed into a whiteboard explainer image with 2 to 3 modules
Not suitable for:
- Clean white-background architecture diagrams, pure infographics, courseware-style whiteboard diagrams
- E-commerce posters, official account covers, PPT templates, tech blue light, cyber style, 3D rendering
Reference Files
- references/visual-style.md: fixed visual specifications and prompt skeleton. Read when writing the final prompt or when the art style needs to remain consistent.
Core Workflow
Step 1: Distill the whiteboard explanation logic
Distill from the user's content:
- Title: 4 to 12 characters, like a large title on an on-site whiteboard
- Core judgment: the one sentence this image should make people remember
- Structure: prioritize
Problem → Analysis → SolutionorBefore → Process → Result - Key numbers / keywords: 1 to 3, which can be enlarged, circled in red, or underlined
- Visual symbols: people, Agents, documents, computers, clocks, gears, magnifying glasses, warnings, check marks, bar charts, growth arrows, etc.
If the user provides a long text, do not copy the main body; retain at most the title, module names, keywords, short sentences, and key numbers.
Step 2: Organize into an on-site whiteboard layout
Default composition:
- Top: a very large handwritten Chinese title
- Below the title: a line of subtitle or logic chain connected with arrows
- Middle: 2 to 3 modules telling the story, with thick arrows connecting the modules
- Bottom: a striking summary sentence or Quote, with keywords emphasized by red circles, blue underlines, or green check marks
Common module names:
问题 Problem分析 Analysis解决 Solution之前 Before过程 Process结果 Result记忆 Memory自动化 CronAgent
Step 3: Read the fixed visual specification
Before preparing to output the final prompt or calling imagegen, read references/visual-style.md, and merge into the final prompt its photographic whiteboard feel, Marker strokes, color scheme, layout, text rules, and things to avoid.
Step 4: Deliver the prompt or generate the image directly
- User only wants the prompt: output the final prompt.
- User explicitly wants an image: after organizing the final prompt, call
imagegen/image_gen。 - User asks for multiple directions: give at most 3 different whiteboard story structures, and keep every direction in a realistic office whiteboard style.
Prompt Writing Rules
The final prompt must include:
- "Generate a 16:9 horizontal realistic office whiteboard hand-drawn explainer image"
- Whiteboard photographic feel: frame, slight reflections, eraser marks, dust, residual pen marks, pen tray, eraser, whiteboard markers, slightly blurred office meeting room background
- Hand-drawn feel: thick black Marker, slightly shaky lines, imperfect, diagonal scribble fill, simple stick-figure icons and people
- Color scheme: black for the main body, blue for the main flow, red for key points / errors / warnings, green for solutions / success / check marks, a small amount of yellow for light bulbs or inspiration
- Text: mainly Chinese, short and clear, like whiteboard handwriting, mixed Chinese and English allowed
- Prohibited: no PPT template style, flat vector style, tech blue glow, cyber style, clean UI, card-based design, gradient backgrounds, refined illustrations, 3D rendering, overly smooth icons
Output Modes
Default output prompt
# 真实办公室白板手绘生图提示词
**建议比例**:16:9
## 最终提示词
[可直接用于 imagegen 的完整提示词]
Generate the image directly
When the user explicitly asks to generate an image, use the organized complete prompt to call imagegen / image_gen. After generation, only give a brief response, do not output lengthy analysis.
Do / Don't
Do
- Make the image look like a real meeting room whiteboard photo
- First distill the story structure, then arrange the modules
- Explain clearly with thick Marker, circles, underlines, arrows, and simple symbols
- Control the amount of text so keywords are readable
- Keep eraser marks, residual pen marks, reflections, and whiteboard objects
Don't
- Do not make it a pure white background vector infographic
- Do not copy the user's original text onto the whiteboard in full paragraphs
- Do not use large-area gradients, tech blue glow, glass texture, or 3D
- Do not make it a card-based UI or PPT template
- Do not make the whiteboard too clean, too much like a commercial illustration, or too smooth