hig-components-content — Claude Code skill: setup and features
Provides Apple Human Interface Guidelines for content components like charts and collections. It helps choose standard controls across Apple platforms.
npx skills add raintree-technology/hig-doctor --skill hig-components-content -a claude-codeWhat hig-components-content does
This skill applies Apple Human Interface Guidelines to UI content decisions. It covers when to deploy Swift Charts, UICollectionView, WKWebView, SFSafariViewController, or tvOS lockup cards. Before prompting for project details, it checks .claude/apple-design-context.md to avoid redundant questions.
Outputs follow a structured format with component recommendations, setup properties, and accessibility rules such as audio graphs and VoiceOver labels. It distinguishes platform behavior directly, contrasting compact touch cells on iOS with parallax cards on tvOS and depth effects on visionOS.
The skill prioritizes built-in system components over custom UI views. Because standard Apple components handle platform adaptations natively, writing custom rendering views requires clear justification.
What it helps with
- choose appropriate Apple components for charts and quantitative data
- configure accessibility requirements like audio graphs and VoiceOver labels
- decide between WKWebView and SFSafariViewController for web content
- adapt collection views and cards for tvOS or visionOS conventions
Example prompts for the agent
- Which Apple HIG component should I use to display a grid of products?
- Should I use WKWebView or SFSafariViewController for external terms of service?
- How do I configure accessibility for Swift Charts under Apple guidelines?
How to install hig-components-content
1Skills CLI (Vercel)
npx skills add raintree-technology/hig-doctor --skill hig-components-content -a claude-code2Manually: put the files in place
~/.claude/skills/hig-components-content/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/hig-components-content/
1Skills CLI (Vercel)
npx skills add raintree-technology/hig-doctor --skill hig-components-content -a codex2Manually: put the files in place
.agents/skills/hig-components-content/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add raintree-technology/hig-doctor --skill hig-components-content -a cursor2Manually: put the files in place
.cursor/skills/hig-components-content/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install raintree-technology/hig-doctor hig-components-content2Manually: put the files in place
.github/skills/hig-components-content/SKILL.md1Skills CLI (Vercel)
npx skills add raintree-technology/hig-doctor --skill hig-components-content -a gemini-cli2Platform CLI
gemini skills install https://github.com/raintree-technology/hig-doctor --path skills/hig-components-contentManually: put the files in place
.devin/skills/hig-components-content/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add raintree-technology/hig-doctor --skill hig-components-content -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about hig-components-content
How do I install hig-components-content in Claude Code?
Run npx skills add raintree-technology/hig-doctor --skill hig-components-content -a claude-code in your terminal.
What does hig-components-content do?
It provides guidance from Apple Human Interface Guidelines on presenting images, charts, collections, and web content.
What is the role of .claude/apple-design-context.md?
The skill inspects .claude/apple-design-context.md first to read existing project conventions before asking follow-up questions.
Source text
SKILL.md · MIT
--- name: hig-components-content version: 1.0.0 description: >- Apple Human Interface Guidelines for content display components. Use this skill when the user asks about "charts component", "collection view", "image view", "web view", "color well", "image well", "activity view", "lockup", "data visualization", "content display", displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says "how should I display charts", "what's the best way to show images", "should I use a web view", "how do I build a grid of items", "what component shows media", or "how do I present a share sheet". Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior. --- # 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)*
© raintree-technology · MIT · raintree-technology/hig-doctor