hig-components-status
Skill153 starsChanged 9 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ozgurakkaya90/claude-skillsword for word, first seen Aug 2, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ozgurakkaya90/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hig-components-contentSkill
- hig-components-controlsSkill
- hig-components-dialogsSkill
- hig-components-layoutSkill
- hig-components-menusSkill
- hig-components-searchSkill
- hig-components-systemSkill
- hig-foundationsSkill
- hig-inputsSkill
- hig-patternsSkill
- hig-platformsSkill
- hig-project-contextSkill
- hig-technologiesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Check for .claude/apple-design-context.md before asking questions.
- Distinctive: line 38
Respect safe areas: No interactive content behind the status bar.
- Distinctive: line 40
Restore the status bar promptly: when exiting immersive contexts.
- Distinctive: line 42
Activity rings are for Move, Exercise, and Stand goals: Don't repurpose the ring metaphor for unrelated data.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.