Conciseness

The body is code-dense and assumes Claude's competence with almost no general-concept padding, but the ~10-line Contents TOC duplicates section headings and Common Mistakes/Review Checklist partially restate material also present in the reference files. Matches the 4 anchor (efficient, minor instances that could be trimmed); not 5 because a few tokens (TOC, checklist overlap) do not earn their place, and not 3 because the padding is minor.

Actionability

Every common case has executable, copy-paste-ready Swift: Map view with markers/controls, Annotation, MapPolyline/Polygon/Circle, MapCameraPosition variants, selection binding, CLLocationUpdate.liveUpdates() tracking task with accuracy filtering, CLServiceSession, authorization-denied Settings UI, CLGeocoder, MKGeocodingRequest, MKLocalSearchCompleter/ MKLocalSearch, MKDirections + route drawing, ETA, and PlaceDescriptor. Matches the 5 anchor; placeholder variables (routeCoords, applePark) are standard illustrative names and coverage of common cases is comprehensive.

Workflow Clarity

Five clearly sequenced numbered workflows cover the distinct task types, and the Review Checklist provides a validation pass for the review workflow. Matches the 4 anchor (clear sequence, most checkpoints present, minor gaps): individual build workflows lack inline verification steps (e.g., workflow 2 does not inline the denial-handling step it covers elsewhere). Not 5 because no explicit validate→fix→retry loop is embedded in the workflows, though none is strictly required since these are not destructive/batch operations.

Progressive Disclosure

Verified against the actual bundle: two well-named reference files one level deep, with every cited anchor (references/mapkit-patterns.md#complete-map-view-setup, #map-in-a-list-or-scrollview, #cycling-directions-ios-14) resolving to real headings. The intro's conditional pointers ('Read X when you need...') clearly signal when to load each file, and the References section annotates both files' scope. Matches the 5 anchor (clear overview, well-signaled one-level-deep references, easy navigation).

Specificity

Concrete actions ('Implement, review, or improve') are followed by an exhaustive enumeration of specific capabilities: 'Map views, annotations, markers, polylines, user location tracking, geocoding, reverse geocoding, search/autocomplete, directions and routes, geofencing, region monitoring, CLLocationUpdate async streams, or location authorization flows'. This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it is not 4 because there are no notable coverage gaps.

Completeness

Explicitly answers 'what' ('Implement, review, or improve maps and location features in iOS/macOS apps using MapKit and CoreLocation') and 'when' with two concrete 'Use when working with...' trigger clauses. This is the 5 anchor pattern verbatim; not 4 because the 'when' guidance is fully explicit rather than weakly implied.

Trigger Term Quality

Two trigger sentences cover natural keywords users would actually say — 'maps', 'annotations', 'markers', 'user location tracking', 'search/autocomplete', 'directions and routes', 'geofencing' — plus synonyms in the second clause ('coordinates, addresses, places, distance calculations, or location-based features in Swift apps'). Matches the 5 anchor's comprehensive synonym coverage; not 3 because common variations are all present.

Distinctiveness Conflict Risk

'MapKit and CoreLocation' scoped to 'iOS/macOS apps' is a clear niche with domain-specific triggers (CLMonitor-style terminology, geofencing, CLLocationUpdate). Matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk); the only overlap is the intended Swift location-feature scope itself, so it is not 4.