Content
65%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.
A tightly written, highly concrete design-system spec that a model could largely build from directly, weakened by a missing production workflow (no sequenced steps or validation checkpoints in the body) and by references to seed files (example.html, STYLE_PRESETS.md, LICENSE) that are not shipped in the bundle. The repeated lock rules could also be consolidated for token efficiency.
Suggestions
Ship the referenced files (example.html, STYLE_PRESETS.md, LICENSE) in the bundle — or inline the essential seed CSS/JS and preset definition — so the "keep verbatim" instructions are executable.
Add a short numbered workflow in the body: ask for missing essentials → produce slide plan → write slides from masters → run a self-check (contrast, overflow, single-idea-per-slide, forwardable-without-rewriting critic pass).
Consolidate the three repeated color/typeface lock statements into one "Locked constraints" list to trim redundant tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a dense design spec — exact :root tokens, a master-page table, a scaling formula, and a nav key list — with no padding and no explanation of concepts Claude already knows. Not 5: the lock rules are repeated three times ("do not introduce any color or font outside this spec", "Forbidden: any other hue…", "Never substitute … any second typeface") and could be consolidated. | 4 / 5 |
Actionability | Provides concrete, executable guidance: the full :root CSS block, the split-panel HTML shell, "factor = min(innerWidth/1920, innerHeight/1080)", master split ratios, and a precise output contract. Not 5 because the pivotal instruction to keep "example.html" and its SlidePresentation controller "verbatim" cannot be executed — no example.html ships in the bundle, and the seed CSS/JS is not inlined. | 4 / 5 |
Workflow Clarity | The sequence is only implied (start from the seed → compose masters → emit a single self-contained HTML), with no ordered steps for the actual production process and no validation checkpoints — "No scrolling, no overflow" is stated as a constraint rather than a check. Matches anchor 3 (sequence present but implicit, checkpoints missing); the ask-essentials → plan → write → critic-pass flow lives only in the frontmatter example prompt. | 3 / 5 |
Progressive Disclosure | Section headers are clear (tokens, typography, layout, masters, stage, motion, output, attribution), but the referenced files — example.html, STYLE_PRESETS.md, and the LICENSE — do not exist in the bundle (no references/, scripts/, or assets/ directories), so the references do not resolve. Good signaling but broken structure lands at 3 rather than 4, and above 2 because organization within the file is solid. | 3 / 5 |
Total | 14 / 20 Passed |