hig-components-content

Apple Human Interface Guidelines for content display components.

31,392 stars
Complexity: easy

About this skill

This skill equips an AI agent with specialized knowledge derived from Apple's Human Interface Guidelines (HIG), specifically focusing on content display components. It serves as a comprehensive reference for agents when discussing, evaluating, or generating advice related to designing user interfaces according to Apple's standards. Instead of an external API call, this skill functions by providing internal context and principles (like adaptability, accessibility, and visual hierarchy) that the agent should consult before answering questions, ensuring design recommendations are accurate, relevant, and aligned with HIG best practices. It directs the AI to reference a specific context file, enhancing its ability to provide expert guidance on Apple's design philosophy for UI elements.

Best use case

Designing iOS/macOS applications, evaluating UI/UX designs against Apple standards, educating users on HIG principles, generating content component specifications, providing design feedback, and answering specific questions about Apple's approach to content display.

Apple Human Interface Guidelines for content display components.

The AI agent will provide accurate, detailed, and HIG-compliant advice regarding Apple content components, demonstrating a deep understanding of core principles like adaptability, accessibility, and visual hierarchy, backed by the provided guidelines.

Practical example

Example input

How should I design a list view for an iOS app to ensure it's accessible and adapts well to different screen sizes, according to Apple's Human Interface Guidelines?

Example output

According to Apple's Human Interface Guidelines for content components, your list view should prioritize adaptability and accessibility. For adaptability, use Auto Layout and size classes to ensure it works across various screen sizes, orientations, and multitasking configurations. For accessibility, make sure each item has proper VoiceOver navigation order, clear labels, and descriptions. Consider providing audio graph support if the list contains data visualizations to enhance accessibility.

When to use this skill

  • When an AI agent is asked questions about Apple's design principles, user interface guidelines for content display, accessibility best practices for Apple platforms, or needs to provide design feedback aligned with HIG for components like lists, charts, or images.

When not to use this skill

  • For general design advice unrelated to Apple platforms, for technical implementation details beyond design principles, when discussing design systems other than Apple HIG, or when the query does not specifically involve content display components.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/hig-components-content/SKILL.md --create-dirs "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/plugins/antigravity-awesome-skills-claude/skills/hig-components-content/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/hig-components-content/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How hig-components-content Compares

Feature / Agenthig-components-contentStandard Approach
Platform SupportClaudeLimited / Varies
Context Awareness High Baseline
Installation ComplexityeasyN/A

Frequently Asked Questions

What does this skill do?

Apple Human Interface Guidelines for content display components.

Which AI agents support this skill?

This skill is designed for Claude.

How difficult is it to install?

The installation complexity is rated as easy. You can find the installation instructions above.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 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 Auto Layout and size classes.

2. **Make content accessible.** Charts need audio graph support. Images need alt text. Collections need proper VoiceOver navigation order. All content components need labels and descriptions.

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

4. **Use system components first.** Evaluate UICollectionView, SwiftUI Charts, WKWebView before building custom. System components come with built-in accessibility and platform adaptation.

5. **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.

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

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

## Reference Index

| Reference | Topic | Key content |
|---|---|---|
| [charts.md](references/charts.md) | Charts | Swift Charts, bar/line/area/point marks, chart accessibility, audio graphs |
| [collections.md](references/collections.md) | Collections | Grid/list layouts, compositional layout, selection, reordering, diffable data sources |
| [image-views.md](references/image-views.md) | Image Views | Aspect ratio handling, content modes, SF Symbol images, accessibility |
| [image-wells.md](references/image-wells.md) | Image Wells | Drag-and-drop image selection, macOS-specific, placeholder content |
| [color-wells.md](references/color-wells.md) | Color Wells | Color selection UI, system color picker, custom color spaces |
| [web-views.md](references/web-views.md) | Web Views | WKWebView, SFSafariViewController, navigation controls, content restrictions |
| [activity-views.md](references/activity-views.md) | Activity Views | Share sheets, activity items, custom activities, action extensions |
| [lockups.md](references/lockups.md) | Lockups | Image+text elements, tvOS card layouts, focus effects, shelf layouts |

## Component Selection Guide

| Content Need | Recommended Component | Platform Notes |
|---|---|---|
| Visualizing quantitative data | Charts (Swift Charts) | iOS 16+, macOS 13+, watchOS 9+ |
| Browsing a grid or list of items | Collection View | Compositional layout for complex arrangements |
| Displaying a single image | Image View | Support aspect ratio fitting; provide accessibility description |
| Selecting an image via drag or browse | Image Well | macOS primarily; use image pickers on iOS |
| Selecting a color | Color Well | Triggers system color picker; macOS, iOS 14+ |
| Showing web content inline | Web View (WKWebView) | Use SFSafariViewController for external browsing |
| Sharing content to other apps | Activity View | System share sheet with configurable activity types |
| Content card (image + text) | Lockup | Primarily tvOS; adaptable to other platforms |

## 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.

Related Skills

hig-components-dialogs

31392
from sickn33/antigravity-awesome-skills

Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.

Design GuidelinesClaude

iconsax-library

31392
from sickn33/antigravity-awesome-skills

Extensive icon library and AI-driven icon generation skill for premium UI/UX design.

Design GuidelinesClaude

hig-platforms

31392
from sickn33/antigravity-awesome-skills

Apple Human Interface Guidelines for platform-specific design.

Design GuidelinesClaude

hig-foundations

31392
from sickn33/antigravity-awesome-skills

Apple Human Interface Guidelines design foundations.

Design GuidelinesClaude

hig-components-system

31392
from sickn33/antigravity-awesome-skills

Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts.

Design GuidelinesClaude

hig-components-status

31392
from sickn33/antigravity-awesome-skills

Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.

Design GuidanceClaude

hig-components-menus

31392
from sickn33/antigravity-awesome-skills

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

Design GuidanceClaude

hig-components-layout

31392
from sickn33/antigravity-awesome-skills

Apple Human Interface Guidelines for layout and navigation components.

Design GuidanceClaude

hig-components-controls

31392
from sickn33/antigravity-awesome-skills

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

Design GuidanceClaude

core-components

31392
from sickn33/antigravity-awesome-skills

Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.

Code GenerationClaude

content-strategy

31392
from sickn33/antigravity-awesome-skills

Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.

Content MarketingClaude

content-marketer

31392
from sickn33/antigravity-awesome-skills

Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing.

MarketingClaude