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.

referencessheets.md

≈559 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/sheets. 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.

Sheets

Best practices

Use a sheet to present simple content or tasks.

For complex or prolonged user flows, consider alternatives to sheets.

Display only one sheet at a time from the main interface.

Use a nonmodal view when you want to present supplementary items that affect the main task in the parent view.

Platform considerations

iOS, iPadOS

In an iPhone app, consider supporting the medium detent to allow progressive disclosure of the sheet’s content.

Include a grabber in a resizable sheet.

Support swiping to dismiss a sheet.

Position Done and Cancel buttons as people expect.

Prefer using the page or form sheet presentation styles in an iPadOS app.

macOS

Present a sheet in a reasonable default size.

Let people interact with other app windows without first dismissing a sheet.

Position a sheet’s dismiss buttons as people expect.

Use a panel instead of a sheet if people need to repeatedly provide input and observe results.

visionOS

Avoid displaying a sheet that emerges from the bottom edge of a window.

Present a sheet in a default size that helps people retain their context.

watchOS

Use a sheet only when your modal task requires a custom title or custom content presentation.

Keep sheet interactions brief and occasional.

Change the default label of the dismiss control only if it makes sense in your app.

If you change the default label, prefer using SF Symbols to represent the action.


<!-- 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/sheets

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