{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/hig-components-status",
  "version": "1.0.1",
  "name": "Hig Components Status",
  "description": "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.",
  "system_prompt_fragment": "# Apple HIG: Status Components\n\nCheck for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.\n\n## Key Principles\n\n### Progress Indicators\n\n1. **Show progress for operations longer than a second or two.**\n\n2. **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.\n\n3. **Indeterminate when duration is unknown.** A spinner communicates work is happening without promising a timeframe. Use for unpredictable network requests.\n\n4. **Prefer progress bars over spinners.** Determinate progress feels faster and more trustworthy.\n\n5. **Place indicators where content will appear.** Inline progress near the content area, not modal or distant.\n\n6. **Don't stack multiple indicators.** Aggregate simultaneous operations into one representation or show the most relevant.\n\n### Status Bars\n\n7. **Don't hide the status bar without good reason.** Reserve hiding for immersive experiences (full-screen media, games, AR).\n\n8. **Match status bar style to your content.** Light or dark for adequate contrast.\n\n9. **Respect safe areas.** No interactive content behind the status bar.\n\n10. **Restore promptly** when exiting immersive contexts.\n\n### Activity Rings\n\n11. **Activity rings are for Move, Exercise, and Stand goals.** Don't repurpose the ring metaphor for unrelated data.\n\n12. **Respect ring color conventions.** Red (Move), green (Exercise), blue (Stand) are strongly associated with Apple Fitness.\n\n13. **Use HealthKit APIs** for activity data rather than manual tracking.\n\n14. **Celebrate completions** with animation and haptics when rings close.\n\n## Reference Index\n\n| Reference | Topic | Key content |\n|---|---|---|\n| [progress-indicators.md](references/progress-indicators.md) | Progress bars and spinners | Determinate, indeterminate, inline placement, duration |\n| [status-bars.md](references/status-bars.md) | iOS/iPadOS status bar | System info, visibility, style, safe areas |\n| [activity-rings.md](references/activity-rings.md) | watchOS activity rings | Move/Exercise/Stand, HealthKit, fitness tracking, color |\n\n## Output Format\n\n1. **Indicator type recommendation** with rationale (determinate vs indeterminate).\n2. **Timing and animation guidance** -- duration thresholds, animation style, transitions.\n3. **Accessibility** -- VoiceOver progress announcements, live region updates.\n4. **Platform-specific behavior** across targeted platforms.\n\n## Questions to Ask\n\n1. Is the duration known or unknown?\n2. Which platforms?\n3. How long does the operation typically take?\n4. System-level or in-app indicator?\n\n## Related Skills\n\n- **hig-components-system** -- Widgets and complications displaying progress or status\n- **hig-inputs** -- Gestures triggering progress states (pull-to-refresh)\n- **hig-technologies** -- HealthKit for activity ring data; VoiceOver for progress announcements\n\n---\n\n*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.",
  "applicable_domains": [
    "frontend"
  ],
  "category": "frontend",
  "invocation": [
    "/hig-components-status"
  ],
  "authored_by": "claudeskills.in community",
  "source_url": "https://claudeskills.in/skill/hig-components-status",
  "provenance": {
    "source": "claudeskills.in",
    "source_url": "https://claudeskills.in/skill/hig-components-status",
    "license": "unknown",
    "imported_at": "2026-09-03",
    "notes": "Aggregated by claudeskills.in from community GitHub lists."
  },
  "tags": [
    "claudeskills",
    "frontend"
  ],
  "lifecycle": "draft"
}