Hig components status

Skill raintree-technology/hig-doctor/skills/hig-components-status

Apple HIG reference and cross-framework UI audit tooling for agents.

Install

npx -y skills add raintree-technology/hig-doctor --skill hig-components-status

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: "progress indicator", "progress bar", "loading spinner", "status bar", "activity ring", "progress display", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says "how do I show loading state," "should I use a spinner or progress bar," "what goes in the status bar," or asks about activity indicators. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.

SKILL.md

3.8 KB, as published. Nobody here has run it

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

Show progress for operations longer than a second or two.
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.
Indeterminate when duration is unknown. A spinner communicates work is happening without promising a timeframe. Use for unpredictable network requests.
Prefer progress bars over spinners. Determinate progress feels faster and more trustworthy.
Place indicators where content will appear. Inline progress near the content area, not modal or distant.
Don't stack multiple indicators. Aggregate simultaneous operations into one representation or show the most relevant.
Don't hide the status bar without good reason. Reserve hiding for immersive experiences (full-screen media, games, AR).
Match status bar style to your content. Light or dark for adequate contrast.
Respect safe areas. No interactive content behind the status bar.
Restore the status bar promptly when exiting immersive contexts.
Activity rings are for Move, Exercise, and Stand goals. Don't repurpose the ring metaphor for unrelated data.
Respect ring color conventions. Red (Move), green (Exercise), blue (Stand) are strongly associated with Apple Fitness.
Use HealthKit APIs for activity data rather than manual tracking.
Celebrate completions with animation and haptics when rings close.

Reference Index

Reference	Topic	Key content
progress-indicators.md	Progress bars and spinners	Determinate, indeterminate, inline placement, duration
status-bars.md	iOS/iPadOS status bar	System info, visibility, style, safe areas
activity-rings.md	watchOS activity rings	Move/Exercise/Stand, HealthKit, fitness tracking, color

Output Format

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

Questions to Ask

Is the duration known or unknown?
Which platforms?
How long does the operation typically take?
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