SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsmulticolor-system-architecture-ppt

multicolor-system-architecture-ppt

Design & creation

View repository

Updated 10-15 20:12

About this skill

Multicolor System Architecture PPT Infographic

Convert the user's new content into a high-density but orderly 16:9 landscape PPT system architecture infographic, and by default call imagegen skill / built-in image_gen tool to generate the image.

Effect Preview

Effect Preview

assets/preview.png is the 16:9 sample image the user confirmed as satisfactory when creating this Skill, used to demonstrate the target visual style. When generating new images later, there is no need to copy the preview image's content; only reuse its corresponding visual system, layout language, and information organization approach.

Default Settings

  • Aspect Ratio: 16:9 landscape.
  • Image Generation Method: Use the imagegen skill, which underlyingly calls the built-in image_gen tool.
  • Background: White or very light gray-white paper surface, clean, restrained, suitable for presentation slides.
  • Primary Colors: Deep blue, orange, deep green, purple; red is used only for risk, warnings, and error notices.
  • Art Style: Flat vector, thin-line outlines, rounded containers, process arrows, icon lists, file trees, node networks, reuse loops; the number of sections varies with the content and does not follow a fixed template.
  • Text: Short Chinese titles, module labels, extremely short descriptions; avoid long paragraphs and unreadable small text.
  • Default Delivery: When the user asks for an image, image output, accompanying illustration, PPT graphic, or presentation page, organize the final prompt and call image_gen; when the user explicitly asks only for the prompt, do not call image generation.

Applicable Scenarios

  • Explanatory diagrams for AI Agents, Skills, RAG, knowledge bases, workflows, data pipelines, product mechanisms, and system architectures.
  • Input, processing, and output flows, as well as closed-loop systems such as querying, feedback, review, and iteration.
  • Complex PPT pages that need to express the main process, risk points, reuse paths, comparison conclusions, or relationships among multiple subsystems at the same time.
  • When the user explicitly mentions keywords such as "white-background architecture diagram", "multicolor sections", "system flowchart", "high-density infographic", "technical PPT", or "closed-loop process".

Style Guidelines

Canvas and Whitespace

  • The image is 16:9 landscape by default, with narrow margins on all sides, and the main subject occupies 85% to 92% of the image.
  • Organize content with a clear grid: choose 2 to 6 main semantic sections depending on the topic, which may include the main process, closed loop, comparison bar, risk notice, asset area, or result area.
  • Keep even spacing between containers; high information density is allowed, but every block must have clear boundaries.

Background and Texture

  • Use a white or very light gray background, and you may add very slight paper-like grayscale and soft shadows.
  • Do not use dark backgrounds, complex gradients, photos, 3D scenes, or decorative textures.
  • The texture should feel like a professional technical presentation slide, not a poster, webpage, or marketing KV.

Color System

  • Blue blocks represent input, resources, problem sources, or the starting point on the left.
  • Orange blocks represent processing, compilation, generation, analysis, and intermediate mechanisms.
  • Green blocks represent artifacts, knowledge bases, reusable assets, and optimization results.
  • Purple blocks represent query loops, reuse chains, context windows, or auxiliary processes.
  • Red is used only for warning bars, risk labels, error prompts, and nodes that require manual review.
  • Line colors must be consistent with block semantics; avoid turning the entire page into a single tone.

Layout Structure

The overall style is fixed as a white background, multi-color zoning, thin-line containers, and arrow relationships, but the specific number of zones must be determined by the content; do not mechanically apply a fixed three-column layout. Common layouts include:

  • 2 to 3 major zones: suitable for concise comparisons such as problem / solution, input / output, and old way / new way.
  • 3 to 5 main process zones: suitable for a continuous process from resources, processing, and generation to review and accumulation.
  • Center plus peripheral zones: suitable for one core mechanism connecting multiple modules, roles, or capabilities.
  • Top-bottom layered zoning: suitable for system structures such as the foundation layer, processing layer, application layer, and feedback layer.
  • Closed-loop or feedback zones: suitable for cyclic processes such as querying, retrieval, generation, review, and updating.
  • Risk and comparison supplementary zone: add a red warning bar or bottom path comparison only when the content requires it.

Regardless of which structure is used, retain multi-color zoning, thin-line containers, arrow relationships, short labels, and the high-density technical PPT feel.

Graphic Language

  • Use large containers as rounded rectangles with 8 to 16px radius and 1 to 2px thin strokes.
  • Icons should mainly be linear flat icons: documents, folders, magnifying glasses, warning triangles, locks, databases, node networks, dialog boxes, and charts.
  • Arrows may mix thick solid arrows, thin-line arrows, and dashed arrows, but the direction must be clear.
  • File trees, lists, node diagrams, and process cards should look like hand-laid-out PPT elements, not like real software screenshots.

Text Hierarchy

  • Place a prominent Chinese title at the top or in the main visual position; 12 to 24 characters are recommended.
  • Large container titles should be 4 to 12 characters; subtitles may be 8 to 18 characters.
  • List items and node labels should be 2 to 8 characters whenever possible.
  • Place at most 3 to 6 short labels in each block; do not include full paragraphs of explanation.
  • It must be emphasized that text should be clear and readable, and must not overlap, blur into tiny text, or be obscured by arrows.

Items to Avoid

  • Do not replicate the original text, logos, watermarks, real people, proprietary copyrighted characters, or brand assets with uncertain authorization from reference images.
  • Do not include dense tiny English text, meaningless gibberish, or unreadable placeholder text.
  • Do not create a dark tech style, cyberpunk, 3D rendering, photo collage, or decorative poster.
  • Do not let red warning elements overpower the main subject; risk prompts should serve the process expression.

Core Workflow

Step 1: Distill the Content

Compress the user input into information suitable for expression in one complex PPT architecture diagram:

  • One 8 to 24 character Chinese main title.
  • One core argument, used to determine the overall flow direction of the page.
  • 2 to 6 main semantic zones, with the number determined by content complexity.
  • The role of each section, such as input, question, mechanism, stage, module, artifact, risk, review, feedback, or result.
  • 0 to 3 risk alerts or key constraints; add a red warning bar only when the content truly requires it.
  • Optional closed loop: asking, retrieval, selection, generation, feedback, etc.; if the topic is not a cyclic system, it can be changed to a linear process, layered architecture, or left-right comparison.
  • Optional bottom conclusion: old path vs new path, cost vs benefit, temporary solution vs reusable asset, etc.; do not force it in when unnecessary.

If the user provides a long text or article paragraph, first extract the structure; do not stuff the entire original text into the diagram.

Step 2: Apply the layout

First determine the number of sections and structure suitable for the content, then apply the style. Optional structures:

  1. Simple comparison: 2 large sections, suitable for old way / new way, problem / solution.
  2. Horizontal process: 3 to 5 sections, connected with arrows, suitable for stage progression.
  3. Multi-module architecture: 4 to 6 sections, suitable for system components, role collaboration, capability map.
  4. Layered structure: 3 to 4 layers top to bottom, suitable for infrastructure, processing layer, application layer, feedback layer.
  5. Closed-loop structure: 4 to 6 steps forming a loop, suitable for continuous optimization, retrospective, and iteration.
  6. Main process + auxiliary area: besides the main process, add risk alerts, reuse queue, file tree, node network, or bottom comparison as needed.

Do not forcibly generate a fixed three-column layout, fixed closed loop, or fixed bottom comparison just to match the preview image; keep only the overall visual style.

Step 3: Organize the imagegen prompt

Prompt order:

  1. Specify the image type and ratio: 16:9 horizontal PPT technical architecture infographic.
  2. Describe the visual style: white background, multi-color sections, thin-line strokes, rounded-corner containers, arrows, icons, warning bars.
  3. Describe the content structure: main title, number of sections determined by the content, block relationships, risk alerts, closed loop or comparison.
  4. Limit text: short Chinese labels, minimal explanation, clear and readable, no dense small text.
  5. Add negative constraints: no Logo, watermark, original text copy, photos, 3D, dark background, garbled text.

Step 4: Call imagegen

  • When the user explicitly asks for an image, image generation, an accompanying illustration, a PPT image, or to draw one, use the final prompt to call image_gen。
  • When the user explicitly says "only give the prompt," output only the complete prompt and do not call image generation.
  • When generating a series of images, keep the same set of color semantics, rounded corners, strokes, icon style, and information density.

Prompt Template

请生成一张 16:9 横版 PPT 技术架构信息图，风格为“多色系统架构 PPT 信息图”。

主题：[用户主题]
主标题：[8 到 24 字中文标题]
核心表达：[一句话说明这张图要讲清楚什么]

画面结构：
- 根据内容复杂度选择 [2 到 6] 个主要语义分区，不要固定套用三栏。
- 分区布局：[横向流程 / 左右对比 / 上下分层 / 中心放射 / 闭环结构 / 主流程 + 辅助区]。
- 主要分区：[分区 1 名称与角色]、[分区 2 名称与角色]、[分区 3 名称与角色]、[按需增加或减少]。
- 连接关系：用箭头、虚线回流、节点连线或分层连接表达[关系说明]。
- 可选风险提示：如果内容需要，使用红色警示条表达[风险 1]、[风险 2]；不需要则省略。
- 可选结论区：如果内容需要，用浅灰横条或底部短句表达[对比/结论]；不需要则省略。

主要内容：
- [分区 1]：[2 到 5 个短标签]
- [分区 2]：[2 到 5 个短标签]
- [分区 3]：[2 到 5 个短标签]
- [更多分区按内容决定，不要强行填满]
- [辅助区/风险区/闭环区/底部对比]：[按需填写或省略]

视觉要求：白色或极浅灰背景，深蓝、橙色、深绿、紫色分区，红色警示提示；大量细线描边圆角矩形、流程箭头、文档图标、文件夹图标、放大镜、警示三角、数据库、节点连线、对话框和小图表；整体像精心制作的高密度技术演示页。

文字要求：中文短标题和短标签，少量说明，文字必须清晰可读，不要互相遮挡，不要密集小字，不要乱码。

限制：不要 Logo，不要水印，不要真实人物，不要版权角色，不要复刻任何参考图原文，不要暗黑背景，不要赛博朋克，不要 3D 渲染，不要照片拼贴。图片比例必须是 16:9。

Image generation rules

  • When the user says "generate an image / generate the image directly / draw one / accompanying illustration / PPT image / presentation page," call by default image_gen。
  • Before calling, you may briefly organize the final prompt, but do not give a long explanation of the design process.
  • If the user does not give a specific topic, infer it from the context first; if it truly cannot be inferred, ask only one necessary question.
  • Prioritize clear structure and readable text, then pursue information density.