Content
86%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 concise, well-structured body with an accurate resource map, executable workflow steps, and a real validation checkpoint against an existing checklist. The only notable gaps are the high-level design-system mapping instruction and the absence of an explicit fix-and-revalidate loop.
Suggestions
Make step 1 concrete: list the root CSS variables in `assets/template.html` (or point to their location) so 'map palette/typography to root CSS variables' is executable without inspecting the template first.
Add a brief failure path to step 6, e.g., 'If any P0 checklist item fails, fix it in `index.html` and re-validate before emitting the artifact.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~40-line body is lean and purposeful: a resource map, a 6-step workflow, and an output contract, with no explanation of concepts Claude already knows. Not below 5 because every section directly instructs the task and nothing reads as padding. | 5 / 5 |
Actionability | Steps are mostly executable — 'Copy `assets/template.html` to `index.html`', 'Validate against `references/checklist.md` before emitting', and a concrete `<artifact>` output example — and both referenced bundle files exist. Not 5 because 'map palette/typography to root CSS variables' stays high-level without naming the variables or how to map them. | 4 / 5 |
Workflow Clarity | The six-step workflow is clearly sequenced and includes an explicit validation checkpoint (step 6, backed by a real P0 checklist). Not 5 because there is no error-recovery feedback loop (what to do when checklist items fail) before emitting; not 3 because a validation checkpoint is explicitly present and the operation is non-destructive. | 4 / 5 |
Progressive Disclosure | The resource map matches the actual bundle exactly (`assets/template.html` and `references/checklist.md` both exist), references are one level deep, and each is clearly signaled at the workflow step where it is needed. Navigation is trivial in a short, well-sectioned body. | 5 / 5 |
Total | 18 / 20 Passed |