All skills
raintree-technology avatar

/hig-components-dialogs

@71d5f4e

Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this skill when the user says "should I use an alert or a sheet," "how do I show a confirmation dialog," "when should I use a popover," "my modals are annoying users," or asks about alert design, action sheet, popover, sheet, modal, dialog, digit entry, confirmation dialog, warning dialog, modal presentation, non-modal content, destructive action confirmation, or overlay UI patterns. Cross-references: hig-components-menus, hig-components-controls, hig-components-search, hig-patterns.

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

This session only. Nothing lands on disk.

referencesalerts.md

≈746 tokens on demand. Your agent reads this file only when SKILL.md points to it.

<!-- hig-doctor:attribution -->

Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/alerts. This file is a structured index of that content, snapshot 2025-02-02. Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

Alerts

Best practices

Use alerts sparingly.

Avoid using an alert merely to provide information.

Avoid displaying alerts for common, undoable actions, even when they’re destructive.

Avoid showing an alert when your app starts.

Anatomy

  • iOS
  • macOS
  • tvOS
  • visionOS
  • watchOS

Content

  • In iOS, iPadOS, macOS, and visionOS, an alert can include a text field.

  • Alerts in macOS and visionOS can include an icon and an accessory view.

  • macOS alerts can add a suppression checkbox and a Help button.

In all alert copy, be direct, and use a neutral, approachable tone.

Write a title that clearly and succinctly describes the situation.

Include informative text only if it adds value.

Avoid explaining alert buttons.

If supported, include a text field only if you need people’s input to resolve the situation.

Buttons

Create succinct, logical button titles.

Avoid using OK as the default button title unless the alert is purely informational.

Place buttons where people expect.

Use the destructive style to identify a button that performs a destructive action people didn’t deliberately choose.

If there’s a destructive action, include a Cancel button to give people a clear, safe way to avoid the action.

Provide alternative ways to cancel an alert when it makes sense.

Platform considerations

iOS, iPadOS

Use an action sheet — not an alert — to offer choices related to an intentional action.

When possible, avoid displaying an alert that scrolls.

macOS

  • Configure repeating alerts to let people suppress subsequent occurrences of the same alert.

  • Append a custom view if it’s necessary to provide additional information (for developer guidance, see accessoryView).

  • Include a Help button that opens your help documentation (see Help buttons).

Use a caution symbol sparingly.


<!-- hig-doctor:canonical-footer -->

For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/alerts

Source: SKILL.md on GitHub

No alerts17d4 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill provides informational guidance on Apple's Human Interface Guidelines for presentation components. It contains only markdown documentation and links to official Apple developer resources and the author's website. No code or suspicious patterns were detected.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub 4 weeks ago.

Activeupdated 8 months ago
version
1.0.0

README badge

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