Content
80%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.
The body is a tight, well-structured spec sheet with concrete values and clear sections, scoring high on conciseness and progressive disclosure. Its main weakness is the absence of an explicit build/validate workflow and a complete HTML example.
Suggestions
Add a short numbered build sequence with an explicit validation checkpoint (e.g., '1. Pick one palette; 2. Compose each slide; 3. Verify no overflow at 1920x1080; 4. Only then add keyboard nav and corner marks').
Include one complete minimal <section class="slide"> HTML example to make the guidance fully copy-paste ready.
State the overflow check as an explicit verify step rather than only a prohibition, to close the workflow feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and dense: exact type-scale px values, padding tiers, palette hex codes, and font names with no padding or explanation of concepts Claude already knows, so every token earns its place. | 5 / 5 |
Actionability | Concrete executable specs are given (width/height, transform: scale, hex colors, type scale, section markup), but there is no complete copy-paste HTML slide example, leaving a minor gap. | 4 / 5 |
Workflow Clarity | The body is a design spec with clear sections rather than a sequenced multi-step workflow, and while the no-overflow constraint is stated, there is no explicit validation checkpoint or feedback loop. | 3 / 5 |
Progressive Disclosure | Under 50 lines with no external bundle files, the content is well-organized into clearly labeled sections (意图, 硬性技术规格, 调色板, 布局自由度, 字体, 设计细节), meeting the simple-skill exception for a top score. | 5 / 5 |
Total | 17 / 20 Passed |