Generate Apple HIG Content Components

An Apple Human Interface Guidelines reference for choosing and configuring content-display components across iOS, macOS, tvOS, watchOS, and visionOS. Covers eight component types with dedicated reference files: Charts (Swift Charts - bar, line, area, and point marks, chart accessibility, audio graphs), Collections (grid and list layouts, compositional layout, selection, reordering, diffable data sources), Image Views (aspect ratio handling, content modes, SF Symbol images), Image Wells (macOS drag-and-drop image selection), Color Wells (system color picker integration), Web Views (WKWebView versus SFSafariViewController for external browsing), Activity Views (share sheets, custom activities, action extensions), and Lockups (image plus text elements, tvOS card layouts with parallax and focus effects, shelf layouts). Seven key principles guide component selection: adapt to different sizes and contexts via Auto Layout and size classes; make content accessible with audio graph support for charts, alt text for images, and proper VoiceOver navigation order for collections; maintain visual hierarchy through spacing and grouping; prefer system components (UICollectionView, SwiftUI Charts, WKWebView) over custom builds since they come with built-in accessibility and platform adaptation; respect platform conventions, since a collection on tvOS uses large parallax lockups while the same collection on iOS uses compact touch-target cells and on visionOS content gains depth and hover effects; handle empty states with guidance rather than a blank screen; and optimize large datasets with lazy loading, cell reuse, pagination, and prefetching. A component-selection table maps content needs directly to components and their minimum OS versions, for example Charts requiring iOS 16+, macOS 13+, or watchOS 9+, and Color Wells needing macOS or iOS 14+.

Use when choosing or configuring a content-display component for an Apple-platform app - visualizing quantitative data, browsing a grid or list, showing a single image or web content, letting a user pick a color or image, sharing to other apps, or building a tvOS content card. Before asking clarifying questions, check for an existing .claude/apple-design-context.md file and only ask about what it doesn't already cover. Not the right skill for structural layout containers such as scroll views, lists, or split views - that's hig-components-layout - or for foundational styling like color and typography, which belongs to hig-foundations.

Input is the content type, target platform or platforms, whether content is static or dynamic, and roughly how much content there is - a few items versus hundreds or thousands, which affects component choice and optimization strategy. Output follows a fixed four-part format: a component recommendation with rationale referencing the relevant HIG file, configuration guidance on key properties, accessibility requirements for that component, and platform-specific notes.

Points to eight companion reference files (charts.md, collections.md, image-views.md, image-wells.md, color-wells.md, web-views.md, activity-views.md, lockups.md) and sibling skills hig-foundations, hig-patterns, hig-components-layout, and hig-platforms for adjacent HIG guidance.

iOS, macOS, tvOS, watchOS, or visionOS developers choosing the right native component for displaying content, who need the accessibility requirements and platform-specific behavior differences spelled out rather than re-reading Apple's full HIG.