mcpField
H
hig-components-status

hig-components-status

github.com/raintree-technologyDesign & UI148654 installsUpdated 6d ago
Repository

About hig-components-status

hig-components-status is a skill for applying Apple HIG guidance to progress indicators, status bars, and activity rings. It helps designers and developers select indicators and account for timing, accessibility, and platform behavior.

Key features

  1. 01Progress indicator selection guidance
  2. 02Timing and animation recommendations
  3. 03Accessibility guidance
  4. 04Status bar and safe area guidance
  5. 05Activity ring usage guidance

Use cases

  1. 01Choosing progress feedback for a known or unknown duration
  2. 02Planning accessible updates for long-running operations
  3. 03Designing status bar behavior around immersive content

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/raintree-technology/hig-doctor --skill hig-components-status

After installing, type/hig-components-statusin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
activity-rings.md
progress-indicators.md
status-bars.md

Details

From the project README

Apple HIG: Status 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. Show progress for operations longer than a second or two.

  2. Determinate when duration/percentage is known. A filling progress bar gives users a clear sense of remaining work. Use for downloads, uploads, or any measurable process.

  3. Indeterminate when duration is unknown. A spinner communicates work is happening without promising a timeframe. Use for unpredictable network requests.

  4. Prefer progress bars over spinners. Determinate progress feels faster and more trustworthy.

  5. Place indicators where content will appear. Inline progress near the content area, not modal or distant.

  6. Don't stack multiple indicators. Aggregate simultaneous operations into one representation or show the most relevant.

  7. Don't hide the status bar without good reason. Reserve hiding for immersive experiences (full-screen media, games, AR).

  8. Match status bar style to your content. Light or dark for adequate contrast.

  9. Respect safe areas. No interactive content behind the status bar.

  10. Restore the status bar promptly when exiting immersive contexts.

  11. Activity rings are for Move, Exercise, and Stand goals. Don't repurpose the ring metaphor for unrelated data.

  12. Respect ring color conventions. Red (Move), green (Exercise), blue (Stand) are strongly associated with Apple Fitness.

  13. Use HealthKit APIs for activity data rather than manual tracking.

  14. Celebrate completions with animation and haptics when rings close.

Reference Index

ReferenceTopicKey content
progress-indicators.mdProgress bars and spinnersDeterminate, indeterminate, inline placement, duration
status-bars.mdiOS/iPadOS status barSystem info, visibility, style, safe areas
activity-rings.mdwatchOS activity ringsMove/Exercise/Stand, HealthKit, fitness tracking, color

Output Format

  1. Indicator type recommendation with rationale (determinate vs indeterminate).
  2. Timing and animation guidance -- duration thresholds, animation style, transitions.
  3. Accessibility -- VoiceOver progress announcements, live region updates.
  4. Platform-specific behavior across targeted platforms.

Questions to Ask

  1. Is the duration known or unknown?
  2. Which platforms?
  3. How long does the operation typically take?
  4. System-level or in-app indicator?

Related Skills

  • hig-components-system -- Widgets and complications displaying progress or status
  • hig-inputs -- Gestures triggering progress states (pull-to-refresh)
  • hig-technologies -- HealthKit for activity ring data; VoiceOver for progress announcements

Built by Raintree Technology · More developer tools

Comments

Markdown supported