Fähigkeiten Apple HIG: Presentation Components
📋

Apple HIG: Presentation Components

Sicher

Apple HIG: Dialogs & Modals

Get Apple Human Interface Guidelines for alerts, sheets, popovers, and action sheets. Choose the right modal pattern for each platform and avoid common UX mistakes with user-interrupting dialogs.

Unterstützt: Claude Codex Code(CC)
🥉 73 Bronze
1

Die Skill-ZIP herunterladen

2

In Claude hochladen

Gehe zu Einstellungen → Fähigkeiten → Skills → Skill hochladen

3

Einschalten und loslegen

Teste es

Verwendung von "Apple HIG: Presentation Components". Should I use an alert or action sheet for delete confirmation?

Erwartetes Ergebnis:

Use an action sheet on iPhone when there are multiple choices (Delete vs Save Draft). Use an alert when it's a simple confirmation with two buttons (Confirm Delete vs Cancel). The action sheet slides up from the bottom on iPhone, making it clear there are multiple options.

Verwendung von "Apple HIG: Presentation Components". How do I handle destructive actions in alerts?

Erwartetes Ergebnis:

Mark destructive buttons with red text using the destructive role. Place destructive buttons at the top where users are less likely to tap reflexively. Always include a Cancel button. Avoid making the destructive button the default.

Verwendung von "Apple HIG: Presentation Components". When should I use sheets instead of full-screen modals?

Erwartetes Ergebnis:

Use sheets for focused tasks that benefit from maintaining context with the underlying content. Sheets slide in from the edge (iOS) or attach to a window (macOS). Ideal for creating items, editing settings, or multi-step forms where seeing the parent content is helpful.

Sicherheitsaudit

Sicher
v1 • 2/25/2026

All static findings are false positives. The skill contains Apple's Human Interface Guidelines documentation for UI presentation components. The flagged patterns (backticks, URLs, generic English words) are legitimate documentation elements, not security threats.

5
Gescannte Dateien
507
Analysierte Zeilen
3
befunde
1
Gesamtzahl Audits
Probleme mit mittlerem Risiko (1)
references/action-sheets.md:13references/alerts.md:104references/sheets.md:27
Markdown Code Formatting (False Positive)
Static scanner flagged backticks as shell execution. These are markdown code fences used to format API references like `UIAlertController.Style.actionSheet`. No executable code present.
Probleme mit niedrigem Risiko (2)
references/action-sheets.md:3references/alerts.md:9references/sheets.md:3
Documentation URL References (False Positive)
Static scanner flagged hardcoded URLs. These are legitimate references to Apple's official developer documentation at developer.apple.com.
references/alerts.md:66references/alerts.md:17references/action-sheets.md:45
Generic English Words (False Positive)
Static scanner flagged words like 'encrypt', 'server', 'system', 'command' as security keywords. These are normal terms in Apple's HIG documentation (e.g., 'secure text field', 'server connection', 'system-defined style').
Auditiert von: claude

Qualitätsbewertung

45
Architektur
100
Wartbarkeit
85
Inhalt
50
Community
96
Sicherheit
74
Spezifikationskonformität

Was du bauen kannst

Choosing confirmation dialog type

User wants to confirm a destructive action (delete, erase, remove). Skill recommends alert vs action sheet based on platform and provides button styling guidance.

Modal presentation decision

User asks 'should I use a sheet or a popover?' Skill explains when sheets maintain context better and when popovers work on iPad/Mac.

Reducing alert fatigue

User complains about too many modals in their app. Skill suggests inline alternatives, undo patterns, and when to avoid interrupting the user.

Probiere diese Prompts

Basic component guidance 
Should I use an alert or an action sheet for [use case]?
Platform-specific behavior 
How does [component] behave differently on iPhone vs iPad?
Button and text guidelines 
What are the best practices for alert button labels and ordering?
Alternative patterns 
What are alternatives to using a modal for [scenario]?

Bewährte Verfahren

  • Use alerts sparingly and only for critical situations requiring immediate attention
  • Provide specific, actionable button labels (Delete, Save) instead of generic OK/Cancel
  • Always include a Cancel button for destructive action confirmations

Vermeiden

  • Using alerts for informative messages that could be shown inline
  • Placing destructive actions as the default button
  • Using the same component for all modal scenarios without considering alternatives

Häufig gestellte Fragen

When should I use an alert vs a sheet?
Use alerts for critical interruptions requiring immediate response. Use sheets for focused tasks where maintaining context with the underlying content is helpful.
Can I use the same design across iPhone and iPad?
Not always. Action sheets appear as popovers on iPad. Sheets adapt differently. Always test on target platforms.
How many buttons should an alert have?
Up to three buttons maximum. Use one button for simple acknowledgment, two for confirm/cancel, three when a destructive option exists.
What is the cancel button placement?
Place Cancel at the bottom of action sheets (iOS) or leading side (macOS). On watchOS, place in upper-left corner.
Should I use OK or specific button labels?
Always prefer specific labels like Delete, Save, or Confirm. Use OK only for purely informational alerts.
How do I make modals accessible?
Ensure voiceover announces the title, message, and all button options. Support keyboard navigation for macOS modals.

Entwicklerdetails

Autor

sickn33

Lizenz

MIT

Repository

https://github.com/sickn33/antigravity-awesome_skills/tree/main/skills/hig-components-dialogs

Ref

main

Dateistruktur

📁 references/

📄 action-sheets.md

📄 alerts.md

📄 digit-entry-views.md

📄 popovers.md

📄 sheets.md

📄 SKILL.md