Content
78%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 exceptionally lean routing overview with excellent progressive disclosure to real, one-level-deep reference files and a clear precedence-ordered workflow. Its main weakness is actionability: the 'Other designs' instructions lean on delegated jargon ('apply acceptance checks', 'resolve installed links once') without concrete steps.
Suggestions
Spell out what the 'Other acceptance, affected editing/interaction and requested supported export checks' concretely involve — at minimum name the specific checks or give a one-line example — rather than delegating entirely to references.
Make 'Resolve installed links once; report missing references without other-checkout searches' operationally concrete: state what resolving a link means and what a report should contain.
Add an explicit pre-completion validation step (e.g., what to verify before declaring an edit complete) so the edit workflow has a visible checkpoint instead of an implied one.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 25-line body is pure telegraphic instruction — "Hand off by manifest category before source reads/edits or shared/type guidance; retain the category." — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the lean anchor 5. | 5 / 5 |
Actionability | The routing table links, exact paths ("design/<session-id>/", "design-tokens.css"), and "--ipw-*" token names are concrete, but directives like "Apply Other acceptance, affected editing/interaction and requested supported export checks; disclose unverified results" provide no concrete steps or examples of what those checks entail. Some concrete guidance exists but key execution details are missing, matching anchor 3 rather than 4. | 3 / 5 |
Workflow Clarity | The sequence is explicit (hand off before reads/edits, then read source, read affected rules, apply checks, resolve links once) and checkpoints are stated ("Stale selection requires a new locator before edits", acceptance/export checks, "report missing references"). This matches anchor 4 with most checkpoints present; it is not 5 because the validation details are delegated to references with no explicit validate-fix-retry loop. | 4 / 5 |
Progressive Disclosure | The body is a lean overview router that clearly signals one-level-deep references — [Other rules](references/design-other.md), [Design authoring](references/design.md), [Shared guidance](references/shared-guidelines.md) — all of which exist in the bundle. Content is appropriately split and navigation is easy, matching anchor 5. | 5 / 5 |
Total | 17 / 20 Passed |