Index of every page on this site: llms.txt
All skills
raintree-technology avatar

/hig-components-status

@a0f1e4e
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/raintree-technology/hig-doctor/hig-components-status

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈180 tokens for metadata: the name and description. ≈767 when used: this file. ≈1.4k more on demand in 3 files.

Description uses 9.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈721 characters, or 9.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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

  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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides design guidance based on the Apple Human Interface Guidelines for status and progress components. It is a documentation-only skill containing no executable code, network operations, or security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    2/4 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at a0f1e4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 9 months ago
version
1.0.0

README badge

README badge for raintree-technology/hig-doctor/hig-components-status