Content
85%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 exceptionally dense and actionable, with exact commands, file shapes, a complete example, and validated multi-step workflows. Its main weaknesses are missing referenced reference files (progressive disclosure is a promise the bundle doesn't keep) and over-detailed editor-behavior narration in Sharing/History.
Suggestions
Ship the ten referenced files (format.md, craft.md, diagrams.md, print.md, questions.md, view-state.md, design-system-components.md, brand-colors.md, brand-typography.md, make-from-this.md) under artifact-type/reference/, or inline their essential rules — as delivered, the body delegates core artboard syntax (repeats, branches, <sc-for>/<sc-if>/<dc-import>) to files that do not exist.
Trim Sharing and History to what the agent must do (share/comment commands, role semantics, the plain-http security caveat) and move the editor-UI narrative (merge-conflict bars, "Put my change back" flows, presence avatars) into a reference file.
Break the single giant canvas.json bullet in "The canvas's files" into labeled sub-bullets (boards entry, order, notes, pages/launch, designSystems) so the index rules are scannable rather than one run-on paragraph.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is aggressively compressed and assumes competence throughout ("Rules that bite (each fails silently)", telegraphic rule lists, no explanation of concepts Claude already knows). It is not a 5 because the Sharing and History sections narrate editor UI behavior in detail the agent rarely needs to act on (merge bars, "Yours was kept", "Put my change back" flows, avatar cards), a noticeable amount of over-included material. | 4 / 5 |
Actionability | Guidance is fully executable: exact CLI calls with their JSON outputs ("upload <root> <file> → {url:\"/_blob/<id>\", …}"), the exact canvas.json shape, a complete copy-paste-ready artboard HTML example, and a ready-to-write git pre-commit hook script. This matches the top anchor of copy-paste-ready commands covering the common cases. | 5 / 5 |
Workflow Clarity | Creating is a numbered sequence (steps 1–6) with an explicit validation feedback loop — "run `check` and fix what it names until `problems` is 0" — and Revising repeats the pattern (steps 1–4, check until problems is 0). Error-recovery paths are also specified (failed uploads become labelled placeholders, NETWORK_BLOCKED handling), matching the anchor with explicit validation steps and feedback loops. | 5 / 5 |
Progressive Disclosure | References are clearly signaled and one level deep with when-to-read guidance ("format.md (before a first artboard)", "diagrams.md (FIRST for diagrams)"), but none of the ten referenced artifact-type/reference/*.md files exist in the bundle — the only files there are google-fonts JSONs — so the critical rules delegated to them (repeats, branches, child components, craft) are unreachable. Signaling alone cannot rate 4 when the disclosed navigation is broken against the actual bundle structure, though the in-body organization keeps it above the minimal-structure anchors. | 3 / 5 |
Total | 17 / 20 Passed |