1. NOW

   ：确认当前任务是否命中本 skill 的适用范围

2. NOW

   ：读取

   ../tool-index.md

   ，校验工具可用性和实际路径

3. NEXT

   ：缺工具时调用 bootstrap，不要猜路径

4. ACT

   ：进入"工作流"第一步并执行，不要停在确认状态

1. Identify the user's intent, audience, and source material.
2. Choose the diagram family and language using the decision table below.
3. Normalize entities, relationships, labels, states, branches, and time/order information before writing diagram code.
4. Generate concise, readable diagram source.
5. Validate the syntax mentally and, when creating files, run

   scripts/render_diagram.py

   .
6. Return the diagram source plus a short note about assumptions. When files are generated, include links to the output files.

• Always provide editable source unless the user explicitly asks only for an image.
• Default to a single best diagram. Offer alternatives only when genuinely useful.
• Prefer stable, simple syntax over fancy features that may not render in older Mermaid/PlantUML versions.
• Use short labels. Split long text into notes outside the diagram when needed.
• Avoid ambiguous node IDs. Use ASCII IDs and human-readable labels.
• Preserve user terminology, but standardize capitalization within a diagram.
• For technical diagrams, include boundaries such as client, service, database, queue, external API, and operator/user when they are implied.
• For business-process diagrams, distinguish happy path, decision points, failures, retries, and manual steps when present.
• For diagrams created from uncertain text, include an

  Assumptions

  section after the code.

references/diagram-patterns.md

• Start with the correct diagram directive, for example

  flowchart TD

  ,

  sequenceDiagram

  ,

  erDiagram

  ,

  gantt

  ,

  mindmap

  , or

  journey

  .
• For flowcharts, use

  flowchart TD

  unless the user asks for left-to-right; use

  flowchart LR

  for architecture and pipelines.
• Use subgraphs for swimlanes or architecture layers. Name subgraphs with readable labels.
• Keep node IDs stable and ASCII-only, for example

  ingest_service[Ingest Service]

  .
• Quote labels that contain punctuation likely to confuse the parser.
• Use decision diamonds for branching:

  decision{Condition?}

  .
• Use consistent edge labels:

  -- yes -->

  ,

  -- no -->

  ,

  -. async .->

  , or

  == critical ==>

  only when meaningful.
• In sequence diagrams, declare participants before messages. Use

  actor

  for humans and

  participant

  for systems.
• Use

  alt/else/end

  ,

  opt/end

  ,

  loop/end

  , and

  par/and/end

  blocks for conditional, optional, repeated, and parallel flows.

• Prefer

  digraph G

  for directed relationships and

  graph G

  for undirected networks.
• Set layout-friendly graph attributes at the top:

  rankdir=LR

  ,

  nodesep

  ,

  ranksep

  , and

  splines=true

  when helpful.
• Use

  subgraph cluster_name

  for boundaries and subsystems.
• Use plain labels and restrained styling.
• Use edge labels only when they add meaning.
• For many nodes, group by domain with clusters and avoid crossing-heavy all-to-all edges.

• Wrap diagrams with

  @startuml

  and

  @enduml

  .
• Use

  actor

  ,

  participant

  ,

  database

  ,

  queue

  ,

  collections

  , or

  component

  stereotypes when useful.
• Use

  package

  ,

  rectangle

  , or

  node

  for architecture boundaries.
• For class diagrams, include only important fields/methods unless the user asks for exhaustive detail.
• For activity diagrams, use clear start/end markers and explicit branch labels.

• Keep SVG simple, accessible, and editable.
• Include

  <title>

  and meaningful text labels.
• Prefer rectangles, lines, arrows, and groups over complex paths.
• Do not embed external fonts or remote images.

python "<SKILL_ROOT>/diagram-generator/scripts/render_diagram.py" input.mmd --format svg --out output.svg
python "<SKILL_ROOT>/diagram-generator/scripts/render_diagram.py" input.dot --format png --out output.png
python "<SKILL_ROOT>/diagram-generator/scripts/render_diagram.py" input.puml --format svg --out output.svg

<SKILL_ROOT>

是本包

skills/

目录的实际路径，AI 应自动检测。

• The diagram type matches the user's task.
• The source is syntactically plausible for the chosen language.
• Labels are short enough to fit.
• Edges and message order reflect the input accurately.
• Assumptions are called out when the input was incomplete.
• For generated files, the output exists and opens or has nonzero size.

下面是可编辑的 [language] 版本：

```[language]
[source]

• [only if needed]

For English user requests, respond in English. For Chinese user requests, respond in Chinese unless they ask otherwise.

---

skills/SKILL.md

routing.md

• 生成的图表可嵌入

  docs-generator/

  的报告中
• 攻击路径图可配合

  pentest-tools/

  的渗透报告

docs-generator/

• 我是否执行了工作流中的每一步（而不是只阅读）？
• 我是否基于

  tool-index

  使用了真实工具路径？
• 我是否产出了可复现证据（命令/脚本/截图/报告）？
• 我是否完成并回写了 RULES 要求的 Checklist 项？