# Design Apple Status and Progress Interfaces

Unclear progress and status feedback can make Apple platform interfaces feel stalled or inconsistent. This skill applies Apple HIG guidance to indicators, status bars, and Activity rings.

## Install

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

## Metadata

- Status: approved
- Slug: sickn33-hig-components-status
- Skillstore revision: r2
- Version status: missing
- Tree hash: 1a8290ab07238adb7c0fead9fd64e64f3627268eff5f65b6aba9f29af6a7d26b
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/hig-components-status
- 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-status
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-hig-components-status/manifest

## Capabilities

- Recommends determinate or indeterminate progress indicators based on task duration and measurability.
- Reviews indicator placement, movement, labels, cancellation controls, and completion transitions.
- Evaluates status bar visibility, readability, safe-area handling, and immersive presentation behavior.
- Checks Activity ring use against Apple Fitness purpose, color, margin, labeling, and ownership rules.
- Provides platform-specific guidance for iOS, iPadOS, macOS, and watchOS where supported.
- Structures recommendations around rationale, timing, animation, accessibility, and platform behavior.

## Use Cases

- Choose Loading Feedback: Select an appropriate indicator and behavior for downloads, uploads, refreshes, or other waiting states.
- Review Apple Platform UI: Audit status bars and progress states for clarity, consistency, safe-area handling, and platform conventions.
- Validate Fitness Displays: Check Activity ring usage, appearance, data meaning, and platform support before implementation.

## Prompt Templates

### Choose an Indicator

```
Choose a progress indicator for [operation]. Its duration is [known or unknown], it usually takes [time], and the target platform is [platform].
```

### Review a Progress Flow

```
Review my [screen or flow] for progress feedback. Recommend indicator type, placement, labels, cancellation behavior, and completion transitions for [platform].
```

### Assess a Status Bar

```
Assess this status bar design for [iOS or iPadOS]. Check readability, content overlap, visibility, immersive transitions, and restoration behavior.
```

### Audit a Fitness Experience

```
Create an HIG review for this [health or fitness app] across [platforms]. Evaluate Activity ring purpose, ownership, color, margins, labels, notifications, and accessibility.
```

## Limitations

- The skill provides design guidance and does not implement or test production interfaces.
- Recommendations depend on accurate task duration, platform, context, and user-flow details.
- Activity rings are limited to Move, Exercise, and Stand data for one person.
- Apple guidance can change, so teams should verify final decisions against current official documentation.

## Best Practices

- Provide the target platform, expected duration, and whether progress can be measured.
- Describe cancellation consequences and any transition from unknown to known progress.
- Include screenshots or flow details when requesting layout, readability, or placement guidance.

## Anti Patterns

- Do not request a determinate percentage when the operation cannot measure real progress.
- Do not use multiple competing indicators for one operation or place feedback far from affected content.
- Do not repurpose Activity rings for unrelated metrics, decoration, branding, or multiple people.

## Security Audit

- Audited at: 2026-07-23T23:34:54.431\+00:00
- Summary: All nine static findings are false positives caused by ordinary documentation prose, Markdown formatting, image descriptions, and benign links. No executable commands, runtime network requests, system reconnaissance, prompt injection, or other malicious intent were found.

## Stats

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