Conciseness

The body is dense and rule-forward with no filler explaining concepts Claude already knows — no React tutorial, no 'what is a slide deck' prose — and it delegates per-primitive detail to `references/*.md` ("This file keeps only the always-on rules and a short summary per primitive"). The duplication is real but minor: the Anti-patterns section and the Self-review checklist restate rules already given verbatim (overflow/split-the-page, padding bounds, notes export, design const), which fits anchor 4 ('minor instances ... that could be trimmed') rather than 5 ('every token earns its place').

Actionability

Guidance is fully executable and copy-paste ready across common cases: the starter template (`export const design: DesignSystem = { ... }` full component code), the page-location command `grep -n ": Page = " slides/<id>/index.tsx`, the timestamp command `node -e "console.log(new Date().toISOString())"`, the worked 816px vertical-budget table with the formula, and the ready-to-run `npx --no playwright screenshot --viewport-size "1920,1080" --wait-for-selector '[data-osd-preview="ready"]' ...` command. This matches anchor 5; not a 4 because no key detail is missing.

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation and feedback loops: the preview procedure is a numbered 4-step flow (find server.json → open preview URL → wait for `[data-osd-preview="ready"]` → screenshot at 1920×1080) that enumerates error states (`[data-osd-preview="error"]` with causes) and instructs "Fix the cause rather than screenshotting anyway", followed by "view the image and fix what you see". A full 17-item Self-review checklist closes the process. This matches anchor 5 (explicit validation steps, error-recovery loops, checklist); not a 4 because checkpoints are explicit, not implicit.

Progressive Disclosure

Excellent structure: an up-front navigation table mapping each primitive to its reference file with a "Read before" condition, per-section "Read `references/X.md` before…" signals, and the stated policy of keeping only always-on rules inline. All 7 referenced files (`design-system.md`, `assets.md`, `webfonts.md`, `page-numbers.md`, `steps.md`, `transitions.md`, `morph.md`) exist in the bundle and are exactly one level deep — matching anchor 5 with no nesting, buried references, or content that should have been split out.

Specificity

The description comprehensively enumerates concrete capabilities ("file contract, 1920×1080 canvas, type scale, layout, palette/visual direction, assets, speaker notes, stepped reveals, page transitions, and morph transitions"), matching the anchor-5 example of multiple specific actions with comprehensive coverage. However, the judging guidelines penalize non-third-person voice by 1 point: "Consult this whenever you are about to write or modify" is second person, so the score is reduced from 5 to 4. It is not a 3 because the action coverage is far richer than '1-2 concrete actions'.

Completeness

It explicitly answers both what ("Technical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, ... morph transitions") and when ("Consult this whenever you are about to write or modify any file under `slides/<id>/`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit" plus a concrete trigger-phrase list). This matches the anchor-5 example exactly — clear 'what' plus explicit 'when' with concrete trigger phrases — so a 4 (vaguely-specified 'when') does not fit.

Trigger Term Quality

Triggers on a wide set of natural user phrasings with synonyms: "edit slide", "tweak this page", "fix the layout", "change the palette", "reveal one by one", "add a transition", "morph transition", "write the speaker notes", "generate the script / talk track", "preview / screenshot a page", "check how it looks", "investigate the slide framework", "how do slides work here". This is comprehensive coverage of natural terms including synonyms (paths like `slides/<id>/` and `index.tsx` stand in for file extensions), matching the anchor-5 example; not a 4 because no common variation is obviously missing.

Distinctiveness Conflict Risk

The niche is clear — open-slide pages under `slides/<id>/`, with explicit coordination against sibling skills (`create-slide`, `apply-comments`, `current-slide`) — and most triggers are slide-specific ("morph transition", "reveal one by one", "preview / screenshot a page"). But several listed phrases ("fix the layout", "change the palette", "check how it looks") are generic and could also fire for ordinary frontend/design work, giving minor overlap risk with closely related skills — anchor 4. It is not a 5 because those generic phrases are not scoped to the slides domain.