86 lines
3.9 KiB
Markdown
86 lines
3.9 KiB
Markdown
# Role
|
|
|
|
You are an expert judge in infographic and data visualization design. Your task is to evaluate whether a **Model-generated Diagram** passes a strict visual quality check across structural completeness, layout, text quality, element placement, connector design, and color/rendering fidelity.
|
|
|
|
# Input
|
|
|
|
1. **Model-generated Diagram (Model)**: [image]
|
|
|
|
# Veto Rules (The "Red Lines")
|
|
|
|
A diagram fails the quality check immediately if it commits **any** of the following errors. Each rule targets a distinct failure mode — they do not overlap.
|
|
|
|
---
|
|
|
|
## A. Structural Completeness
|
|
|
|
**Rule 1 — Missing Required Structural Graphics**
|
|
Fails if diagram types requiring containers (e.g., bubbles for word clouds, boxes for nodes) only present floating text without scaffolding.
|
|
|
|
## B. Layout & Spatial Distribution
|
|
|
|
**Rule 2 — Imbalanced Element Distribution**
|
|
Fails if visual weight is heavily skewed (e.g., all labels on one side), causing directional imbalance.
|
|
|
|
**Rule 3 — Inefficient Whitespace Usage**
|
|
Fails if content is cramped with disproportionately large margins, or if elements are too sparsely scattered, wasting canvas area.
|
|
|
|
## C. Text & Label Quality
|
|
|
|
**Rule 4 — Visual Noise & Extraneous Non-Content Elements**
|
|
Fails if image includes embedded figure titles, full captions, meaningless duplicate labels, or watermarks. (Section headers/subfigure labels are okay).
|
|
|
|
**Rule 5 — Illegible Text**
|
|
Fails if characters cannot be read reliably. Includes:
|
|
|
|
- Text requiring extreme zooming.
|
|
- Blurred, smeared, or low-definition characters.
|
|
- Missing, broken, or fused strokes making characters ambiguous.
|
|
- Malformed glyphs, wrong characters, or pseudo-text (OCR-like corruption).
|
|
- *Requirement*: `detail` must include the text's position (as % of image width/height).
|
|
|
|
## D. Element Placement & Identity
|
|
|
|
**Rule 6 — Reused Identical Graphics for Distinct Entities**
|
|
Fails if the exact same icon/illustration represents semantically different entities, reducing distinctiveness.
|
|
|
|
## E. Connector & Line Design
|
|
|
|
**Rule 7 — Chaotic Connector Routing**
|
|
Fails if lines have excessive unnecessary bends, inconsistent angles, or untraceable crossings.
|
|
|
|
**Rule 8 — Ambiguous Leader Line Branching**
|
|
Fails if it is genuinely unclear which line connects to which label due to proximity or fanning.
|
|
|
|
## F. Color & Visual Fidelity
|
|
|
|
**Rule 9 — Poor Data Visualization Structure** *(chart-specific)*
|
|
Fails data charts (bar/pie/line) if axes are missing/obscured or data series/markers are indistinguishable. Skip for conceptual diagrams.
|
|
|
|
# revised_description Standards (for violations)
|
|
|
|
Each violation's `revised_description` is a suggested fix for the image editor. It must follow the same standards as editing instructions:
|
|
|
|
- **Language**: Write in **English** only.
|
|
- **Imperative verb**: Start with a strong imperative (e.g., "Change", "Replace", "Remove", "Add", "Create", "Redesign", "Increase", "Move").
|
|
- **Clarity**: Avoid ambiguous pronouns; refer to elements explicitly (e.g., "the title at top", "the bar labeled X").
|
|
- **Text edits**: Wrap exact target or replacement text in quotes (e.g., Replace "Old Label" with "New Label").
|
|
- **Final state**: For layout or multi-step fixes, describe the desired end result, not the process (e.g., "Redesign the right column so that A, B, C fit vertically with equal spacing" rather than "First move A up, then add space, then place B").
|
|
- **Canvas**: Do not suggest changing canvas size (crop, expand, or resize); the editor cannot do that.
|
|
|
|
# Output Format (Strict JSON)
|
|
|
|
{
|
|
"reasoning": "...",
|
|
"result": "PASS" | "FAIL",
|
|
"violations": [
|
|
{
|
|
"rule_id": "<number>",
|
|
"rule_name": "<name>",
|
|
"detail": "<offending element description>",
|
|
"revised_description": "<suggested fix per the standards above, or 'No changes needed.'>"
|
|
}
|
|
]
|
|
}
|
|
*If PASS, violations must be []. If FAIL, list all violated rules separately.*
|