FrancoStino/hig-components-status
bundled-skills/hig-components-status/SKILL.md
Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.
$ install --global
skillsauthnpx skillsauth add FrancoStino/opencode-skills-antigravity hig-components-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 27, 2026, 2:54 AM257.2s4 files scanned
SKILL.md
- name:
- hig-components-status
- description:
- Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.
- risk:
- safe
- source:
- community
- date_added:
- 2026-02-27
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
Progress Indicators
-
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.
Status Bars
-
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 promptly when exiting immersive contexts.
Activity Rings
-
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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
FrancoStino/llm-security
tools
VerifiedTrustedCommunity
Authorized security assessment of LLM applications and AI agents: prompt injection, tool abuse, RAG exposure, memory poisoning, system-prompt extraction, and agent-compliance engineering per OWASP LLM/ASI Top 10.
68SKILL.mdUpdated Aug 30, 2026
FrancoStino/liuguang-banlan-ui
development
VerifiedTrustedCommunity
Builds two parameterized UI modes—流光溢彩白 (iridescent white) and 五彩斑斓黑 (colorful black)—with OKLCH, WebGL/CSS fallback, vision gating, screenshot QA, and total/per-color intensity reports. Use when a UI request names either mode or needs measured color parameters.
68SKILL.mdUpdated Aug 30, 2026
FrancoStino/kimi-delegate
tools
VerifiedTrustedCommunity
Delegate coding tasks to the Kimi Code CLI (`kimi`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.
68SKILL.mdUpdated Aug 30, 2026
FrancoStino/js-reverse
development
VerifiedTrustedCommunity
Front-end JavaScript reverse engineering: locate signature chains, analyze encrypted request parameters, sample runtime behavior, and reproduce logic locally in Node for evidence-based output.
68SKILL.mdUpdated Aug 30, 2026