Effect Preview

Convert the user's new content into a 16:9 horizontal PPT infographic with a blackboard writing texture, and by default use the imagegen skill / built-in image_gen tool to generate the image.
Default Settings
- Aspect Ratio: 16:9 horizontal.
- Image Generation Method: Use the
imagegenskill, which calls the built-inimage_gentool at the underlying level. - Background: Deep black-gray realistic blackboard, with chalk eraser marks, graininess, and slight signs of use; the outer ring may have a wooden frame.
- Main Colors: White chalk for the main text and main outlines; light blue for module boxes, arrows, and auxiliary emphasis; yellow for key titles; a small amount of light red or pink for an emphasis area on one side.
- Art Style: Chalk hand drawing, classroom blackboard writing, technical architecture explanation diagram; lines may have slight jitter, without pursuing perfectly straight lines.
- Text: Chinese short titles, short labels, and a small number of bullets; imitating a Chinese chalk handwritten font, and must be clearly readable.
- Default Delivery: When the user asks for an image, image generation, illustration, PPT image, presentation page, or diagram, organize the final prompt and call
image_gen. When the user explicitly only wants the prompt, do not call image generation.
Applicable Scenarios
- Technical concept explanations such as AI Agent, MCP, context engineering, workflow automation, skill systems, knowledge bases, and product architecture.
- Architecture diagrams with one core concept and multiple peripheral modules, methodology framework diagrams, and workflow breakdown diagrams.
- Left-right comparison diagrams of old way vs. new path, problem side vs. solution side, and input side vs. output side.
- Course PPTs, horizontal illustrations for WeChat official accounts, sharing pages, and explanatory infographics.
- When the user explicitly mentions keywords such as "blackboard", "chalk", "blackboard writing", "hand-drawn architecture diagram", "technical architecture", or "classroom explanation style".
Style Specifications
- Aspect Ratio and White Space: Horizontal 16:9, with the main subject concentrated in the middle of the image; leave blackboard margins and wooden frame space around the edges; keep clear spacing between modules to avoid arrows and text pressing against each other.
- Background Texture: The blackboard is not pure black; it should have deep gray layers, chalk dust marks, erasure traces, and fine grain; the wooden frame only serves as outer atmosphere and does not compete for attention with the information.
- Layout Structure: By default use "central radial + left-right zoning". Large title at the top; core node in the middle; place problems, inputs, reach, or the old way on the left; place paths, outputs, workflows, or the new way on the right; cloud mechanism nodes may be placed at the top; supporting mechanisms or closed-loop nodes may be placed at the bottom.
- Text Hierarchy: The top title is the largest, centered, and paired with a white chalk underline; section titles use yellow chalk text; module text uses white; key words may use yellow. Within a single box, prioritize 2 to 10 Chinese characters and avoid long sentences.
- Graphic Elements: Hand-drawn rounded rectangles, hand-drawn large frames, cloud frames, arrows, underlines, short bullets, small labels, and a small amount of chalk doodles. Generalized decorations such as small rockets, stars, lightning bolts, and toolboxes may be used, but they must not become the main subject.
- Information density: Suitable for 1 main title, 1 core node, and 3 to 5 peripheral modules, with each module having 1 to 3 short pieces of text. The information should look like an instructor's live blackboard writing, not a dense poster.
- Items to avoid: Do not copy the original text, watermarks, account names, brand logos, proprietary characters, or identifiable materials from reference images; do not use realistic photography, cyberpunk, 3D rendering, neon light effects, complex gradients, dense small text, or long paragraphs.
Core Workflow
Step 1: Refine the content
Compress the user input into information suitable for expression as a blackboard architecture diagram:
- An 8 to 18 Chinese-character title that summarizes the core judgment.
- A central node that explains the true core mechanism, system, or method.
- 1 to 2 modules on the left, representing surface-level practices, problems, inputs, outreach methods, or the old path.
- 1 to 2 modules on the right, representing the true path, outputs, workflow, goals, or the new path.
- 1 mechanism node at the top, which may represent long-term memory, accumulation, strategy, principles, or sources.
- 1 support node at the bottom, which may represent review, feedback, knowledge base, closed-loop optimization, or version iteration.
If the user provides a long text, do not directly carry over the original text; first rewrite it into short labels and module relationships.
Step 2: Apply the layout
Prefer the default structure:
- Top-centered title + white chalk underline.
- A central white hand-drawn rounded rectangle carrying the core concept.
- A large white frame on the left, containing 1 to 2 light blue small frames, representing the problem side or input side.
- A large pale red frame on the right, containing 1 to 2 light blue small frames, representing the solution side or output side.
- A light blue cloud frame at the top, with an arrow pointing to the center.
- A white support frame at the bottom, with an arrow pointing to the center.
It may also be slightly varied according to the content into a horizontal process, top-bottom layering, or closed-loop cycle, but it must retain the blackboard chalk, hand-drawn frame lines, arrow convergence, and classroom explanation feel.
Step 3: Organize the imagegen prompt
Write the prompt in this order:
- Clearly specify the image type and ratio: 16:9 horizontal PPT infographic, blackboard chalk hand-drawn technical architecture diagram style.
- Describe the visual style: deep black-gray blackboard, wooden frame, chalk eraser smudges, hand-drawn frame lines, slight jitter.
- Describe the theme and structure: title, central node, left modules, right modules, top mechanism, bottom support.
- Describe the text rules: short Chinese labels, chalk handwriting, minimal text, clear and readable.
- Add negative constraints: no watermark, no account name, no real logo, do not copy reference image text, no dense small text, no occlusion.
Step 4: Call imagegen
- When the user explicitly asks to "generate an image / directly produce an image / draw one / pair it with an image / PPT image / presentation page," use the final prompt to call
image_gen。 - If the user only wants the prompt, output only the complete prompt.
- When generating a series of images, keep the same blackboard background, wooden frame, chalk colors, line thickness, text hierarchy, and module density.
Prompt Template
请生成一张 16:9 横版 PPT 信息图,风格为黑板粉笔手绘技术架构图。
主题:[用户主题]
标题:[8 到 18 字中文标题]
核心表达:[一句话说明这张图要讲清楚什么]
画面结构:中心放射 + 左右分区。顶部居中大标题,标题下方有一条白色粉笔下划线;中间是核心节点;左侧是问题侧、输入侧或旧方式;右侧是解法侧、输出侧或新方式;顶部云朵节点表示长期机制或来源;底部节点表示支撑机制或闭环优化。
主要内容:
- 中心节点:[核心概念,短句]
- 左侧标题:[左侧分区标题]
- 左侧模块 1:[短标签]
- 左侧模块 2:[短标签,可选]
- 右侧标题:[右侧分区标题]
- 右侧模块 1:[短标签]
- 右侧模块 2:[短标签,可选]
- 顶部云朵节点:[短标签,可选]
- 底部支撑节点:[短标签,可选,最多 2 条 bullet]
视觉要求:深黑灰真实黑板背景,带粉笔擦痕、颗粒感和轻微使用痕迹,外圈木质相框;白色粉笔为主文字和主描边,浅蓝用于模块框和箭头,黄色用于重点标题,少量淡红用于右侧强调框;所有线框、箭头、下划线都像手绘粉笔,边缘有轻微抖动;可以加入少量泛化粉笔涂鸦装饰,如小火箭、星星、闪电或工具箱,但不能抢占主体。
文字要求:中文短标签,仿中文粉笔手写字体,标题和模块文字必须清晰可读;不要长段落,不要密集小字。
限制:不要水印;不要账号名;不要真实 Logo;不要复制参考图完整文案;不要真实人物;不要写实摄影;不要赛博朋克;不要 3D 渲染;不要霓虹光效;不要复杂渐变;不要让文字、箭头和框线互相遮挡。图片比例必须是 16:9。
Image generation rules
- When the user explicitly asks to "generate an image / output an image directly / draw a picture / add an illustration / PPT graphic / presentation page," you must call
image_gen。 - Before calling, you may briefly state that the blackboard chalk hand-drawn technical architecture diagram style will be used, but do not give a long explanation of the design process.
- If the user has not given a specific topic, first infer it based on the context; if it truly cannot be inferred, then ask one brief question.
- Do not stuff the user's full long text into the image; it must first be compressed into a title, modules, nodes, and short labels.
Do / Don't
Do
- Use a central node, left and right partitions, cloud-shaped mechanisms, bottom support, and converging arrows to carry the logic.
- Maintain the feel of a blackboard, chalk, hand-drawn lines, classroom explanation, and technical architecture diagram.
- Let yellow emphasize only key titles, and let light blue carry module boxes and connecting lines.
- Ensure the Chinese text is minimal, clear, and readable.
Don't
- Do not replicate watermarks, account names, logos, or the full copy of the reference image.
- Do not make it a pure black poster, a complex tech key visual, a realistic photo, or a 3D scene.
- Do not pile up too many modules, arrows, decorations, and explanatory text.
- Do not let decorative doodles be more prominent than the information structure.