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.
An exemplary progressive-disclosure structure: the body is a lean routing index over five real, topic-split reference files with explicit verification doc pointers and concrete Tailwind mappings. The only notable gap is that the verification step names the owning docs but leaves the actual checks to them, keeping actionability and workflow clarity at 4.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean routing index: every line either maps a change type to a reference file, gives a concrete Tailwind class mapping, or names a verification doc. It assumes Claude's competence (no explanation of React, Tailwind, or basic concepts), matching anchor 5's 'every token earns its place'. | 5 / 5 |
Actionability | Guidance is concrete and executable in most places — exact reference paths ('references/ownership.md'), verification doc paths ('web/docs/test.md', 'web/docs/lint.md', 'packages/dify-ui/docs/testing.md'), and copy-ready class mappings ('w-105 instead of w-[420px]', 'px-2.25 instead of px-[9px]'). It falls short of anchor 5 because 'Verify the changed behavior and complete the owning package's required checks' delegates the actual checks without stating them. | 4 / 5 |
Workflow Clarity | The sequence is legible — route the topic to references, identify the behavior owner/state lifetime/public contract, keep the change within the vertical slice, then verify via named docs — with verification checkpoints present. It sits at anchor 4 rather than 5 because the sequence is implicit rather than enumerated and there is no validate-fix-retry feedback loop for the verification step. | 4 / 5 |
Progressive Disclosure | Verified against the actual bundle: all five referenced files (ownership.md, state.md, data.md, interactions.md, runtime.md) exist in references/, and the body is a clear overview with well-signaled, one-level-deep reference links plus link-reference definitions. Content is appropriately split by topic; the second hop to overlay/form contracts points to external package-owned docs that is pre-announced in the body ('the overlay guide it references'), which is appropriate placement rather than deferred-content chaining. | 5 / 5 |
Total | 18 / 20 Passed |