Content
92%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.
An excellent content body: every section carries Figma-specific knowledge Claude could not infer (gating errors, public vs. internal names, render cost mechanics), the verification workflow has explicit validation and feedback loops, and detail is properly deferred to five well-signaled, verified reference files. Only minor tightening opportunities remain, chiefly the repeated "make each render count" phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, high-signal guidance that assumes competence — public vs. internal API names, gating behavior, render cost model — with no teaching of known concepts. Anchor 4 rather than 5 because "make each render count" is repeated nearly verbatim and a few rationale sentences ("Otherwise you'll burn calls and confuse the user with repeated identical failures") could be trimmed. | 4 / 5 |
Actionability | Fully executable throughout: exact enums ("never emit the invalid alias EASE_IN_OUT"), concrete parameters ("constraint: { type: 'WIDTH', value: 320 }", "quality: \"low\"", "fps: 5"), a copy-paste frame-extraction command ("ffmpeg -ss <t> -i anim.mp4 -frames:v 1 frame_<t>.png"), and polling mechanics ("re-invoke with { fileKey, jobId }"). Matches anchor 5 — copy-paste ready and covers the common cases. | 5 / 5 |
Workflow Clarity | The verification workflow is clearly sequenced (pick moments → size → fps → export → poll → extract → iterate) with an explicit feedback loop ("fix the keyframes/styles and re-export... batch every fix into one pass"), a defined failure path ("Bail out fast on that error. Do not retry"), and a 9-item pre-flight checklist. Matches anchor 5: explicit validation steps, error-recovery loops, and a checklist. | 5 / 5 |
Progressive Disclosure | The body is a genuine overview (~90 lines): API surface, gating, verification workflow, and a reference table giving "When to load" and "What it covers" for each of five docs. All five referenced files exist, are one level deep, and the deep link anchor (#animatable-fields) matches a real heading in motion-patterns.md. Matches anchor 5 — clear overview with well-signaled one-level-deep references. | 5 / 5 |
Total | 19 / 20 Passed |