Conciseness

The body assumes Claude's competence — no concept explanations, no filler — but framing rules are stated twice (step 4's "short form" and again in the recurring-faults checklist) and step 4 is an overloaded paragraph mixing copying, reading craft.md, layout choice, and framing. This fits 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place anchor.

Actionability

Concrete, copy-paste-ready commands are present ("node scripts/film.mjs \"<preview>/?capture=<gold>\" --select '#example' --still --out gold.png", "npm run dev", "film.mjs --gate") alongside exact dimensions (720 × 340, 358 compact) and named API parts (Stage, Act, Bar/Text/Row, data-target, rect()). It falls short of fully executable because the central workflows depend on examples/ and kit/ directories that are not present in the bundle, and no minimal kit/Act usage snippet is inlined to compensate.

Workflow Clarity

Seven clearly sequenced steps (plan → look → story → copy gold → build → choreograph → rehearse) with explicit validation feedback loops: film stills beside the gold, a contact sheet at two widths, "fix the largest visible fault first... re-film", "film.mjs --gate ending 'rehearsal passed' is necessary, not sufficient", a fresh-eye review, and a REHEARSAL.md handover. This matches the anchor with explicit validation steps, feedback loops, and a checklist; anchor 4's 'minor validation gaps' does not apply.

Progressive Disclosure

References are one level deep and well signaled — every citation names the file and its section (e.g. "references/framing.md, Small formats and the page") and all 15 referenced reference files verified to exist, with a closing map section. It is not the clear-anchor-5 case because examples/, kit/, and teaching/ paths referenced throughout do not resolve in the provided bundle, leaving the three example tables and kit instructions without their targets.

Specificity

"Build faux product UI... as a still illustration or an animated demo with a cursor", "Browser and app windows, dashboards, phones, notifications, terminals, bento grids", "framed, masked and cropped", and "React and plain CSS" list multiple concrete actions, output forms, and the tech stack with no material gaps, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

Completeness

It explicitly answers what ("Build faux product UI... framed, masked and cropped the way a marketing page, feature card or docs hero needs them") and when ("Use whenever someone wants a fake or mocked UI..."), with concrete trigger phrases, matching the anchor for both clearly present; anchor 4's weaker 'when' does not apply.

Trigger Term Quality

Natural phrases users would say are covered exhaustively — "fake or mocked UI", "product demo", "walkthrough animation", "hero or feature-card illustration", "product shot", "animated cursor" — and it explicitly anticipates unspoken variants ("even if they never say 'faux UI'"), fitting the comprehensive-synonyms anchor rather than anchor 4's "a few natural terms missing".

Distinctiveness Conflict Risk

"Faux product UI" with mock/demo/product-shot triggers carves a clear niche distinct from real UI development or general design skills; triggers are specific enough that conflict risk is minimal, fitting the clear-niche anchor.