Conciseness

The body is lean and directive with no padding or explanation of concepts Claude already knows (e.g., "Animate state changes or visual properties, not expensive computation"), assuming competence throughout; every token earns its place, matching the score-5 anchor.

Actionability

Concrete API names throughout (withAnimation, .animation(_:body:), PhaseAnimator, KeyframeAnimator, matchedGeometryEffect, .symbolEffect, accessibilityReduceMotion) plus a need-to-mechanism decision table give mostly executable guidance; it falls short of 5 because no code examples are provided and one table row is hedged ("matched transition source plus navigation zoom when available") without naming the API.

Workflow Clarity

The Triage section is a clearly sequenced 5-step process with explicit validation checkpoints ("Test normal interaction, interruption, repeated triggers, and Reduce Motion"), an error-recovery path ("If motion hitches, measure before changing architecture"), and a supporting Review Checklist, matching the score-5 anchor; it is not 4 because checkpoints are explicit rather than implicit.

Progressive Disclosure

The ~90-line body is a well-organized overview with a Contents list, and all three referenced files (references/animation-advanced.md, references/symbol-effects-and-accessibility.md, references/core-animation-bridge.md) exist, are one level deep, and are clearly signaled both inline in the mechanism table and in a dedicated References section; the bulk detail (1,430 lines) is correctly split out, matching the score-5 anchor.

Specificity

"Implement or diagnose SwiftUI motion, including state animations, transitions, springs, keyframes, matched geometry, navigation zoom, and symbol effects" enumerates multiple concrete capabilities with comprehensive domain coverage, matching the score-5 anchor; it is not 4 because there are no meaningful gaps in the mechanism coverage.

Completeness

Both a clear "what" (the enumerated SwiftUI motion capabilities) and an explicit "Use when..." clause are present, but the when-clause is a single general condition ("motion behavior is part of the request") rather than concrete trigger phrases, placing it between anchors 4 and 5 and best fitting 4.

Trigger Term Quality

Terms like "animations", "transitions", "springs", and "motion" are natural user vocabulary, but the trigger phrasing "motion behavior is part of the request" is less natural than what users actually say (e.g., "animate this view", "fade", "animated"), so a few natural variations are missing.

Distinctiveness Conflict Risk

The description carves out a clear niche ("SwiftUI motion") and explicitly routes adjacent domains away ("route layout, navigation state, and performance profiling elsewhere"), giving distinct triggers and minimal conflict risk per the score-5 anchor.