美人鱼图
- 作者仓库星标 11,320
- 作者仓库 Auto-claude-code-research-in-sleep
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @wanshuiyin · 未声明许可证
- 上下文用量评级
- 中等消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- Node.js
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
Mermaid diagram generated successfully.
Files:
figures/<diagram-name>.mmd
figures/<diagram-name>.md
figures/<diagram-name>.png
To re-render manually:
mmdc -i figures/<diagram-name>.mmd -o figures/<diagram-name>.png
第 0 步:飞行前检查
创建输出目录
第 1 步:了解要求并选择图表类型
解析输入:$ARGUMENTS 分析请求并选择最合适的图表类型 阅读下面相应的 Mermaid 语法参考 如果图表涉及数学符号,请应用图表中的数学公式部分中的数学语法规则 识别所有组件、连接和数据流
第 2 步:阅读文档
选择适当的图表类型。首先使用内置的美人鱼知识;如果需要外部文档并且您的环境提供了该文档,请获取最新的语法参考。
第 3 步:生成美人鱼代码并保存文件
生成 Mermaid 代码并保存两个文件: 文件 1:`figures/<diagram-name>.mmd` — 原始 Mermaid 源 `.mmd` 文件仅包含原始 Mermaid 代码,没有 Markdown 栅栏。文件 2:`figures/<diagram-name>.md` — 嵌入 Mermaid 的 Markdown `.md` 文件将相同的 Mermaid 代码包装在 mermaid 代码块中以进行预览渲染,以及简短的标题和描述。
第 4 步:验证 Mermaid 语法(强制)
Codex 必须通过运行 Mermaid CLI (`mmdc`) 来验证生成的 Mermaid 代码。检查 mermaid-cli 是否可用 如果验证失败:仔细阅读错误 修复`.mmd`和`.md`的语法问题
第 5 步:Codex 严格视觉审查和评分(强制)
成功渲染后,Codex 必须读取生成的 PNG 并执行严格的审核:如果结论是 `FIX`,则对 `.mmd` 和 `.md` 进行更正,重新渲染并重新审核,直到达到 `ACCEPT` 或 `MAX_ITERATIONS`。
第 6 步:最终输出摘要
接受后,请出示:
# Mermaid Diagram Generator
Generate high-quality Mermaid diagram code based on user requirements, with file output and verification.
## Constants
- **OUTPUT_DIR = `figures/`** — Output directory for generated files
- **MAX_ITERATIONS = 3** — Maximum refinement rounds for syntax or layout issues
## Workflow: MUST EXECUTE ALL STEPS
### Step 0: Pre-flight Check
# Create output directory
```bash
mkdir -p figures
```
### Step 1: Understand Requirements & Select Diagram Type
Parse the input: **$ARGUMENTS**
1. Analyze the request and choose the most suitable diagram type
2. Read the corresponding Mermaid syntax reference below
3. If the diagram involves mathematical notation, apply the math syntax rules from the **Math Formulas in Diagrams** section
4. Identify all components, connections, and data flow
5. Plan the diagram structure before writing code
### Step 2: Read Documentation
Select the appropriate diagram type. Use built-in Mermaid knowledge first; if external documentation is needed and your environment provides it, fetch the up-to-date syntax reference.
### Configuration & Themes
Choose theme, colors, and layout before writing code. For academic diagrams, prefer clean white backgrounds, restrained colors, and readable labels over decorative styling.
| Type | Use Cases |
| ---- | --------- |
| Flowchart | Processes, decisions, steps |
| Sequence Diagram | Interactions, messaging, API calls |
| Class Diagram | Class structure, inheritance, associations |
| State Diagram | State machines, state transitions |
| ER Diagram | Database design, entity relationships |
| Gantt Chart | Project planning, timelines |
| Pie Chart | Proportions, distributions |
| Mindmap | Hierarchical structures, knowledge graphs |
| Timeline | Historical events, milestones |
| Git Graph | Branches, merges, versions |
| Quadrant Chart | Four-quadrant analysis |
| Requirement Diagram | Requirements traceability |
| C4 Diagram | System architecture |
| Sankey Diagram | Flow, conversions |
| XY Chart | Line charts, bar charts |
| Block Diagram | System components, modules |
| Packet Diagram | Network protocols, data structures |
| Kanban | Task management, workflows |
| Architecture Diagram | System architecture |
| Radar Chart | Multi-dimensional comparison |
| Treemap | Hierarchical data visualization |
| User Journey | User experience flows |
| ZenUML | Sequence diagrams (code style) |
### Step 3: Generate Mermaid Code & Save Files
Generate the Mermaid code and save **two** files:
#### File 1: `figures/<diagram-name>.mmd` — Raw Mermaid source
The `.mmd` file contains only raw Mermaid code, no markdown fences.
#### File 2: `figures/<diagram-name>.md` — Markdown with embedded Mermaid
The `.md` file wraps the same Mermaid code in a mermaid code block for preview rendering, plus a short title and description.
# Diagram Title
Use a concise title in the `.md` wrapper that matches the generated diagram name.
**Naming convention**: use a descriptive kebab-case name derived from the request, such as `auth-flow`, `system-architecture`, or `database-er`.
### Step 4: Verify Mermaid Syntax (MANDATORY)
Codex MUST verify the generated Mermaid code by running the Mermaid CLI (`mmdc`).
# Check if mermaid-cli is available
```bash
if command -v mmdc >/dev/null 2>&1; then
mmdc -i figures/<diagram-name>.mmd -o figures/<diagram-name>.png -b transparent
echo "Syntax valid — PNG rendered to figures/<diagram-name>.png"
else
npx -y @mermaid-js/mermaid-cli@latest -i figures/<diagram-name>.mmd -o figures/<diagram-name>.png -b transparent
echo "Syntax valid — PNG rendered to figures/<diagram-name>.png"
fi
```
If verification fails:
1. Read the error carefully
2. Fix the syntax issue in both `.mmd` and `.md`
3. Re-run verification
4. Repeat up to `MAX_ITERATIONS`
### Step 5: Codex STRICT Visual Review & Scoring (MANDATORY)
After successful rendering, Codex MUST read the generated PNG and perform a strict review:
```markdown
## Codex's STRICT Review of <diagram-name>
### What I See
[Describe the rendered diagram in detail]
### Files Generated
- `figures/<diagram-name>.mmd`
- `figures/<diagram-name>.md`
- `figures/<diagram-name>.png`
### ═══════════════════════════════════════════════════════════════
### STRICT VERIFICATION CHECKLIST (ALL must pass for score ≥ 9)
### ═══════════════════════════════════════════════════════════════
#### A. File Correctness
- [ ] `.mmd` contains valid Mermaid syntax
- [ ] `.md` wraps the Mermaid code in ```mermaid fences
- [ ] `.mmd` and `.md` contain identical Mermaid code
- [ ] Diagram renders without errors
ASCII alias for automated checks: score >= 9.
#### B. Arrow Correctness Verification (CRITICAL - any failure = score ≤ 6)
ASCII alias for automated checks: CRITICAL - any failure = score <= 6.
- [ ] Every arrow points to the correct target
#### C. Block Content Verification (any failure = score ≤ 7)
ASCII alias for automated checks: any failure = score <= 7.
- [ ] Every block label is correct
- [ ] Every block contains the intended content
#### D. Completeness
- [ ] All required components are present
- [ ] All required connections are present
- [ ] Labels are meaningful and match the request
#### E. Visual Quality
- [ ] Layout is clean and readable
- [ ] Colors are professional
- [ ] Text is readable at normal zoom
- [ ] Spacing is balanced
- [ ] Data flow is understandable within 5 seconds
### ═══════════════════════════════════════════════════════════════
### Issues Found (BE SPECIFIC)
1. [issue] -> [fix]
### Score: X/10
### Score Breakdown Guide:
- 10: correct, readable, publication-ready
- 9: minor polish only
- 8: usable but one visual/layout weakness remains
- 7: one content or block-label weakness remains
- 6 or below: arrow direction, missing component, syntax, or semantic error
### Verdict
- [ ] ACCEPT
- [ ] FIX
```
If the verdict is `FIX`, apply corrections to both `.mmd` and `.md`, re-render, and re-review until `ACCEPT` or `MAX_ITERATIONS` is reached.
### Step 6: Final Output Summary
When accepted, present:
```text
Mermaid diagram generated successfully.
Files:
figures/<diagram-name>.mmd
figures/<diagram-name>.md
figures/<diagram-name>.png
To re-render manually:
mmdc -i figures/<diagram-name>.mmd -o figures/<diagram-name>.png
```
## Architecture Diagram Best Practices
When generating `architecture-beta` diagrams, apply these layout techniques for complex diagrams:
### Use Junctions for Layout Control
Think of the diagram as an invisible grid. Use `junction` nodes as virtual anchor points on that grid to precisely control placement. This is especially useful when a direct edge produces unexpected positioning.
Instead of connecting services directly:
```text
lb:R --> L:scim
lb:R --> L:webapi
```
Route through junctions:
```text
junction j_lb_r
lb:R -- L:j_lb_r
junction j_scim_l
j_lb_r:T -- B:j_scim_l
j_scim_l:R --> L:scim
junction j_webapi_l
j_lb_r:B -- T:j_webapi_l
j_webapi_l:R --> L:webapi
```
### Use Edges out of Groups for Floating Components
For services that have no real logical connection but still need stable placement, use a junction combined with `{group}` to anchor them without inventing a semantic edge.
## CVPR/ICLR/NeurIPS Style Guide (for Academic Diagrams)
When the diagram is intended for academic papers, apply these style standards:
### Visual Standards
- Clean white background
- Sans-serif fonts
- Subtle coordinated color palette
- Print-friendly grayscale readability
- Thin professional borders
### Layout Standards
- Horizontal flow for pipelines
- Clear grouping
- Consistent sizing
- Balanced whitespace
### Arrow Standards (MOST CRITICAL)
- Thick strokes
- Clear arrowheads
- Dark colors
- Labeled arrows
- No crossings
- Correct direction
### Color Palette (Academic Professional)
- **Inputs**: Green (`#10B981` / `#34D399`)
- **Encoders**: Blue (`#2563EB` / `#3B82F6`)
- **Fusion**: Purple (`#7C3AED` / `#8B5CF6`)
- **Outputs**: Orange (`#EA580C` / `#F97316`)
- **Arrows**: Dark gray (`#333333` / `#1F2937`)
- **Background**: White (`#FFFFFF`)
### What to AVOID
- Rainbow color schemes
- Thin hairline arrows
- Heavy shadows or glow effects
- 3D effects
- Decorative icons that add no meaning
- Tiny unreadable text
## Math Formulas in Diagrams (KaTeX)
Mermaid supports rendering mathematical expressions via KaTeX. When the diagram content involves formulas, equations, Greek letters, subscripts, superscripts, fractions, or matrices, use KaTeX notation instead of plain-text approximations.
### Supported Diagram Types for Math
Math rendering with `$$...$$` is supported in:
- **Flowcharts** — in node labels and edge labels
- **Sequence Diagrams** — in participant aliases, messages, and notes
### Syntax Rules
1. Wrap math expressions in `$$` inside quoted strings:
```text
A["$$x^2$$"] -->|"$$\\sqrt{x+3}$$"| B("$$\\frac{1}{2}$$")
```
2. Node labels with math must be quoted
3. Mix text and math by placing `$$` only around the math portion
4. Use `\text{}` for non-math text inside `$$`
### Common Math Patterns for ML/Science Diagrams
| Concept | KaTeX Syntax |
| ------- | ------------ |
| Subscript | `$$W_Q$$` |
| Superscript | `$$x^2$$` |
| Fraction | `$$\\frac{QK^T}{\\sqrt{d_k}}$$` |
| Greek letters | `$$\\alpha, \\beta, \\gamma$$` |
| Square root | `$$\\sqrt{d_k}$$` |
| Summation | `$$\\sum_{i=1}^{n} x_i$$` |
| Matrix | `$$\\begin{bmatrix} a & b \\\\ c & d \\end{bmatrix}$$` |
| Softmax | `$$\\text{softmax}(z_i)$$` |
| Norm | `$$\\|\\|x\\|\\|_2$$` |
| Hat/tilde | `$$\\hat{y}, \\tilde{x}$$` |
### Example: Attention Mechanism with Math
```text
flowchart TD
Q["$$Q \\in \\mathbb{R}^{n \\times d_k}$$"]
K["$$K \\in \\mathbb{R}^{n \\times d_k}$$"]
V["$$V \\in \\mathbb{R}^{n \\times d_v}$$"]
scores["$$\\frac{QK^T}{\\sqrt{d_k}}$$"]
softmax["$$\\text{softmax}(\\cdot)$$"]
output["$$\\text{Attention}(Q,K,V)$$"]
Q --> scores
K --> scores
scores --> softmax
softmax --> weighted["$$\\alpha V$$"]
V --> weighted
weighted --> output
```
### When to Use Math vs Plain Text
- Use math when the diagram is for academic or technical audiences and precision matters
- Use plain text when the diagram is for general audiences or math would add clutter
- Default to KaTeX automatically if the request already contains math notation
### Gotchas
- `$$` delimiters must be inside quoted strings
- Very long formulas may overflow node boxes
- Always verify rendering with `mmdc`
## Code Quality Rules
Generated Mermaid code MUST:
1. Have correct syntax that renders directly
2. Have clear structure with proper indentation
3. Use semantic node naming, not `A`, `B`, `C`
4. Include styling when needed
5. Use `<br/>` for line breaks inside node labels, never `\n`
6. Avoid special characters that break Mermaid parsing unless properly quoted
## Output Structure
```text
figures/
├── <diagram-name>.mmd
├── <diagram-name>.md
└── <diagram-name>.png
```
## Key Rules (MUST FOLLOW)
1. Always save files to `figures/`
2. Always generate both `.mmd` and `.md`
3. Always read the relevant syntax guidance before generating code
4. Always verify syntax before accepting
5. Always review the rendered PNG
6. Never accept score < 9
7. Verify every arrow direction
8. Verify every block content
9. Be specific in feedback
10. Fix errors before accepting
11. Use descriptive kebab-case file names
---
User requirements: $ARGUMENTS
章节与文件索引
按说明文件中的顺序排列。
常数
第 0 步:飞行前检查
第 1 步:了解要求并选择图表类型
第 2 步:阅读文档
配置和主题
文件/命令 -> figures/ · figures/<diagram-name>.mmd · .mmd · figures/<diagram-name>.md · .md · auth-flow · system-architecture · database-er
内容校验值 -> 22d19ce7ce77
当前原文的自动摘译,尚未人工审校。
常数
OUTPUT_DIR =
figures/— 生成文件的输出目录 MAX_ITERATIONS = 3 — 语法或布局问题的最大细化轮次配置和主题
在编写代码之前选择主题、颜色和布局。对于学术图表,与装饰样式相比,更喜欢干净的白色背景、内敛的颜色和可读的标签。类型·用例流程图·流程、决策、步骤序列图·交互、消息传递、API 调用类图·类结构、继承、关联