name: drawio-graph-pipeline
description:Use when the user wants use drawio to create any technical diagram - architecture, data flow, flowchart, sequence, agent/memory, or concept map .Trigger on: "画图" "帮我画" "生成图" "做个图" "架构图" "流程图" "可视化一下" "出图" "generate diagram" "draw diagram" "visualize" or any system/flow description the user wants illustrated.
keywords: drawio, graph, drawio-graph, mind-graph, visualization
Drawio Graph Pipeline - Graph Processing Pipeline
Usage Scenarios
Use this pipeline when you need to convert AI-generated original content into professional, structured, and directly publishable Drawio graph format.
Workflow
- Analyze the type and structure of the original content provided by the user
- Identify the content theme, hierarchical relationships, and key information points
- Determine output goals (Drawio graph type, audience, style)
Step 2: Logic Organization (REQUIRED SUB-SKILL)
- REQUIRED SUB-SKILL: Use logic-organizer skill
- Input the original content into logic-organizer
- Obtain structured text with clear hierarchy and rigorous logic
- REQUIRED SUB-SKILL: Use drawio-format-adapter skill
- Convert the logically organized content into standard XML format
- Ensure correct tag semantics and standardized nesting
Step 4: Element Position Adjustment (REQUIRED SUB-SKILL)
- REQUIRED SUB-SKILL: Use drawio-position-adjuster skill
- Adjust the position of elements in the XML file to ensure beautiful layout that meets expectations
- Adjust the size of elements to ensure the overall balance of the graph
Step 5: Beautification and Rendering (REQUIRED SUB-SKILL)
- REQUIRED SUB-SKILL: Use drawio-xml-beautifier skill
- Add visual beautification elements to XML (CSS styles, icons, color schemes)
- Generate the final Drawio graph XML file that can be directly previewed or exported
Step 6: Output Delivery
- Provide complete XML files
- Explain usage methods and follow-up editing suggestions
- Original Agent output text (any format)
- Optional: Target document type (report/manual/guide/presentation)
- Optional: Style preference (business/academic/simple/lively)
Output Specifications
The final output is a .xml file containing:
- Semantic tag structure
- Embedded style definitions
- Responsive layout support