Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Highly actionable content with concrete tools, paths, selectors, and well-sequenced workflows that include explicit feedback loops. The main weakness is conciseness: the core imagegen-first guidance is repeated across several sections and could be consolidated, and some reference-style tables could live in separate files.
Suggestions
Consolidate the repeated 'imagegen-first, don't write SVG' messaging from the 原生能力校准, SVG 复发熔断闸, Full-page raster first, and 什么时候才写 SVG sections into a single decision rule with one short fallback list to remove redundancy.
Consider extracting the DOM 选择器速查 and 下载文件命名 tables into a references/ file referenced once from the browser path section, reducing the main body length and improving progressive disclosure.
Tighten the 注意事项 section by merging items that restate the '优先原生 tool call' and '禁止 CLI 命令替代' rules already covered in the 原生路径 section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Operational rather than concept-explaining, but the 'imagegen-first / don't write SVG' message is restated across four to five sections (原生能力校准, SVG 复发熔断闸, Full-page raster first, 什么时候才写 SVG, Common Mistakes), which is redundant padding that could be consolidated; not a 2 because no basic concepts are over-explained. | 3 / 5 |
Actionability | Provides concrete tool names (image_gen, generate_image), exact artifact paths, specific DOM selectors (.ql-editor, #prompt-textarea), numbered browser steps, and a shell example; fully executable and copy-paste ready across the common cases. | 5 / 5 |
Workflow Clarity | The 'Full-page raster first' workflow has a clear 4-step sequence with an explicit feedback loop (视觉评估 → prompt 迭代 → 失败才降级), the SVG circuit-breaker has a 4-step execution order, and the Common Mistakes table functions as a checklist; image generation is non-destructive so no batch-validation cap applies. | 5 / 5 |
Progressive Disclosure | Single self-contained file with clear section headers and no bundle files, so references are not an issue; however the file exceeds 50 lines and inlines reference-style content (DOM selector tables, file-naming conventions) that could be split out, leaving minor organization gaps versus a 5. | 4 / 5 |
Total | 17 / 20 Passed |