Content
72%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 an exemplary lean router with well-signaled, verified one-level-deep references and disciplined token efficiency. Its weakness is over-compression: key 'Other' workflow steps and validation checkpoints are named in telegraphic prose rather than given as an executable sequence, so following them depends on interpreting references rather than acting directly.
Suggestions
Unpack the telegraphic 'Other' section into a short numbered sequence (read source and tokens, locate stale selection, apply Other rules, run acceptance/export checks, disclose unverified results) so the order and checkpoints are explicit.
State in one line each what 'Other acceptance' and 'affected editing/interaction checks' concretely involve, or point to the exact section in design-other.md that defines them instead of naming them abstractly.
Clarify compressed clauses like 'No replacement project, preview host or application-source edits' and 'assets follow shared media plan/check' — either spell out the prohibited actions or link the specific guideline section being invoked.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~25-line body contains zero padding and zero explanation of concepts Claude already knows — every sentence is a directive ('Preserve --ipw-* tokens/variable bindings', 'No replacement project, preview host or application-source edits'). This matches anchor 5 ('lean and efficient; assumes Claude's competence; every token earns its place'); there are no unnecessary explanations that would pull it to anchor 4. | 5 / 5 |
Actionability | There are concrete elements — the routing table with real links, exact paths ('design/<session-id>/', 'design-tokens.css'), and specific invariants ('--ipw-* tokens', 'component IDs, editable/locked markers'). But much of the 'Other' section is compressed to near-opacity ('Apply Other acceptance, affected editing/interaction and requested supported export checks'; 'assets follow shared media plan/check') — pointers whose execution requires chasing multiple referenced files, matching anchor 3 ('some concrete guidance but incomplete; missing key details') rather than anchor 4's mostly-executable guidance. | 3 / 5 |
Workflow Clarity | An implicit sequence exists (hand off before reads/edits, then read the injected source, then apply rules and acceptance checks, and 'disclose unverified results' acts as a validation/disclosure checkpoint), and 'Stale selection requires a new locator before edits' is a conditional guard. But the steps are embedded in prose rather than sequenced, and checkpoints like 'Apply Other acceptance ... checks' are named, not specified — anchor 3 ('steps present but checkpoints missing or implicit'), not anchor 4's clear sequence with most checkpoints explicit. | 3 / 5 |
Progressive Disclosure | The body is a true overview/router: it keeps only the routing table and the 'Other' summary inline, and points to verified, one-level-deep bundle files with clearly signaled purpose ('Read only affected [Other rules](references/design-other.md) for targeted/theme edits', 'Creation/structural work uses applicable [Design authoring](references/design.md) and [Shared guidance](references/shared-guidelines.md) sections'). All three referenced files exist in references/ with matching sections, and 'Resolve installed links once; report missing references' handles link failures — matching anchor 5. | 5 / 5 |
Total | 16 / 20 Passed |