Conciseness

Lean and dense with project-specific knowledge only (e.g. 'text drawn with dominant-baseline="central" has its visual top about 0.35 × size above its y'; 'Published files are a mix of 1x and 2x; that is history, not a target'). It assumes competence — no explanations of SVG, Chrome, or rendering basics — and no sentence is padding, matching the 5 anchor.

Actionability

Fully executable guidance: exact commands ('grep -rhoE srcLight="[^"]+" docs | sort -u', a concrete curl blob URL, 'CHROME=/path/to/chrome ./render.sh', 'node gen.mjs <name>', 'python3 scripts/measure.py light/<name>.png') and a complete, commented diagram-module template. The sketched draw() body is justified flexibility since each diagram differs, so this is 5 rather than 4.

Workflow Clarity

Six clearly sequenced steps with explicit validation (step 5: 'Look at both PNGs at full size, against review-checklist.md and against the references'; 'Run python3 scripts/measure.py light/<name>.png for the margins'), a feedback loop ('Fix in constants and re-render'), and a hard gate ('Do not hand off a PNG you have not looked at') plus a final name-agreement check — matching the 5 anchor's checkpoints and error-recovery loop.

Progressive Disclosure

The structure is exemplary — a task-to-file table, one-level-deep references, workflow steps linking to the file they need — but scored against the actual bundle, two of the six referenced files ('style-tokens.md' and 'review-checklist.md') do not exist anywhere, and style-tokens.md carries the color semantics ('What the colors mean') that step 1 and the Color convention depend on. A dangling, load-bearing reference is more than the 'minor organization gaps' of the 4 anchor, so this falls to 3.

Specificity

Names multiple concrete actions and specifics: 'Draw diagrams for the Next.js docs in the style of the ones already published', 'the light/dark PNGs an mdx references', 'Hand-written SVG from a primitives library, rendered by headless Chrome at 2x', plus the constraint 'No AI image generation'. Coverage of the niche is comprehensive with no real gaps, matching the 5 anchor rather than 4.

Completeness

Explicitly answers both questions: what ('Draw diagrams... light/dark PNGs... Hand-written SVG from a primitives library, rendered by headless Chrome at 2x') and when ('Use when a guide or API reference needs a new diagram or an existing one needs a change') with two concrete trigger conditions. This matches the 5 anchor exactly; the 'when' clause is present and specific, so no cap applies.

Trigger Term Quality

Good natural keyword coverage: 'diagram' (twice), 'guide', 'API reference', 'PNG', 'new diagram', 'existing one needs a change'. A few natural synonyms a user might say ('illustration', 'figure', 'image', '.png') are missing, which fits the 4 anchor rather than the comprehensive synonym coverage of 5.

Distinctiveness Conflict Risk

Scoped tightly to 'the Next.js docs in the style of the ones already published there' via mdx <Image> light/dark PNG pairs — a clear niche with distinct triggers and minimal conflict risk against generic diagramming or image skills, matching the 5 anchor.