sickn33/antigravity-awesome-skills/hig-components-content

Apple HIG: Content Components

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

1. Adapt to different sizes and contexts. Content components must work across screen sizes, orientations, and multitasking configurations. Use the layout system appropriate to the framework (SwiftUI layout or Auto Layout), and use size classes where available.

1. Make content accessible. Provide chart summaries and appropriate accessible data navigation; Swift Charts includes a default Audio Graphs implementation. Give meaningful images descriptive accessibility labels and hide decorative or redundant images. Collections need a logical VoiceOver navigation order.

1. Maintain visual hierarchy. Use spacing, sizing, and grouping to establish clear information hierarchy. Primary content should be visually prominent.

1. Use system components first. Evaluate UICollectionView, SwiftUI Charts, WKWebView before building custom. System components provide accessibility and adaptation defaults; still test labels, interactions and supported platform versions.

1. Respect platform conventions. A collection on tvOS uses large lockups with parallax. The same collection on iOS uses compact cells with touch targets. On visionOS, content gains depth and hover effects.

1. Handle empty states. Show a meaningful empty state with guidance on how to populate it, not a blank screen.

1. Optimize for performance. Use lazy loading, cell reuse, pagination, and prefetching for large datasets.

Reference Index

Component Selection Guide

Output Format

1. Component recommendation with rationale, referencing the relevant HIG reference file.
2. Configuration guidance -- key properties and setup.
3. Accessibility requirements for the recommended component.
4. Platform-specific notes for targeted platforms.

Questions to Ask

1. What type of content? (Quantitative data, images, web content, browsable collection, share action?)
2. Which platforms?
3. Static or dynamic content?
4. How much content? (Few items vs hundreds/thousands affects component choice and optimization.)

Related Skills

• hig-foundations -- Color, typography, accessibility, and image guidelines
• hig-patterns -- Data visualization, sharing, and loading patterns
• hig-components-layout -- Structural containers (scroll views, lists, split views) hosting content
• hig-platforms -- Platform-specific component behavior (lockups on tvOS, web views on macOS)

Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Example

User request:

Use @hig-components-content for this task: Apple Human Interface Guidelines for content display components.

Limitations

• Bundled HIG pages are reference snapshots, not a live compatibility matrix. Verify API availability against the target SDK and deployment version. macOS uses native sharing APIs rather than UIActivityViewController; do not infer API portability from a shared visual pattern.
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.