# Design Apple Content Components with HIG Guidance

Choosing the right Apple content component requires platform, accessibility, and performance tradeoffs. This skill recommends HIG-aligned components and explains configuration, accessibility, and platform considerations.

## Install

```bash
npx skillstore add sickn33/hig-components-content
```

## Metadata

- Status: approved
- Slug: sickn33-hig-components-content
- Skillstore revision: r2
- Version status: missing
- Tree hash: 9186e00256720b907c5a94c7adff81e7b006cd51462ccd06af9b14b45e67daee
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/hig-components-content
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/sickn33-hig-components-content
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-hig-components-content/manifest

## Capabilities

- Recommends charts, collections, image views, image wells, color wells, web views, activity views, or lockups for specific content needs.
- Explains configuration priorities for layout, interaction, loading, selection, navigation, and content presentation.
- Identifies VoiceOver, Audio Graphs, labeling, contrast, and navigation requirements for accessible content components.
- Provides platform notes for iOS, iPadOS, macOS, tvOS, watchOS, and visionOS.
- Compares chart marks, axis ranges, descriptive content, and interaction choices using bundled HIG guidance.
- Returns a recommendation, rationale, configuration guidance, accessibility requirements, and platform considerations.

## Use Cases

- Plan an iOS content screen: Select a collection, image, web, sharing, color, or chart component for a new iPhone or iPad workflow.
- Prepare component implementation: Translate product requirements into component choices, configuration priorities, accessibility requirements, and platform constraints.
- Review content accessibility: Check charts, images, collections, and interactive content for labeling, navigation, contrast, and assistive technology support.

## Prompt Templates

### Choose a content component

```
Recommend an Apple content component for [content type] on [platform]. Explain the choice, basic configuration, accessibility needs, and important platform constraints.
```

### Configure a selected component

```
Configure a [component] for [content volume] on [platform]. Cover layout, interaction, empty states, performance, accessibility, and relevant system alternatives.
```

### Review an existing interface

```
Review this content interface: [description]. Identify HIG concerns involving hierarchy, navigation, selection, color, labels, VoiceOver, and platform behavior. Prioritize improvements.
```

### Design a cross-platform experience

```
Design a cross-platform content experience for [iOS, macOS, tvOS, watchOS, or visionOS]. Compare suitable components, explain adaptations, and define accessibility and performance requirements.
```

## Limitations

- Uses bundled HIG reference snapshots that may not include later Apple guidance changes.
- Provides design recommendations but does not compile, run, or test application code.
- Needs the content type, target platforms, data volume, and interaction requirements for precise guidance.
- Does not replace accessibility testing, performance profiling, or review on physical devices.

## Best Practices

- Provide the content type, target platforms, item count, interaction model, and accessibility needs.
- Prefer standard system components before requesting custom behavior or presentation.
- Validate recommendations against current Apple documentation and test them with assistive technologies on target devices.

## Anti Patterns

- Request a component recommendation without naming the platform, content type, or expected data volume.
- Treat design guidance as production-ready implementation without compiling, profiling, and testing.
- Use a web view as a general browser or build custom components without a clear product need.

## Security Audit

- Audited at: 2026-07-23T23:18:12.084\+00:00
- Summary: All 20 static findings are false positives. The backticks delimit a Markdown path, the URLs are passive references, and the flagged prose contains design guidance rather than reconnaissance commands. No prompt injection, execution, exfiltration, or other malicious intent was found.

## Stats

- Views: 82
- Downloads: 11
- Favorites: 0
- Popularity score: 0