raintree-technology/hig-doctor

hig-components-dialogs

>- 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 overl…

First seen Feb 15, 2026

Installation

$ npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from raintree-technology/hig-doctor · top by installs.

npx skills add raintree-technology/hig-doctor

Browse all from raintree-technology/hig-doctor

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 122
License LICENSE
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,211 B
  • docs SUMMARY.md 643 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 475 installs

SKILL.md

Apple HIG: Presentation Components

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

  1. Alerts: sparingly, for critical situations. Errors needing attention, destructive action confirmations, or information requiring acknowledgment. They interrupt flow and demand a response.
  1. Sheets: focused tasks that maintain context. Slides in from the edge (or attaches to a window on macOS). Use for creating items, editing settings, multi-step forms.
  1. Popovers: non-modal on iPad and Mac. Appear next to the trigger element, dismissed by tapping outside. For additional information, options, or controls without taking over the screen.
  1. Action sheets: choosing among actions. Present when picking from multiple actions, especially if one is destructive. iPhone: slide up from bottom. iPad: appear as popovers.
  1. Minimize interruptions. Before reaching for a modal, consider inline presentation or making the action undoable instead.
  1. Concise, actionable alert text. Short descriptive title. Brief message body if needed. Button labels should be specific verbs ("Delete", "Save"), not "OK".
  1. Mark destructive actions clearly. Destructive button style (red text). Place destructive buttons where users are less likely to tap reflexively.
  1. Provide a cancel option for alerts and action sheets with multiple actions. On action sheets, cancel appears at the bottom, separated.
  1. Digit entry: focused and accessible. Appropriately sized input fields, automatic advancement between digits, support for paste and autofill.
  1. Adapt presentation to platform. The same interaction may use different components on iPhone, iPad, Mac, and visionOS.

Reference Index

Reference Topic Key content
[alerts.md](references/alerts.md) Alerts Button ordering, title/message text, confirmation, destructive actions
[action-sheets.md](references/action-sheets.md) Action sheets Multiple actions, cancel option, destructive handling
[popovers.md](references/popovers.md) Popovers Non-modal, dismiss on tap outside, iPad/Mac
[sheets.md](references/sheets.md) Sheets Modal task, context preservation
[digit-entry-views.md](references/digit-entry-views.md) Digit entry PIN input, autofill, auto-advance

Output Format

  1. Recommended presentation type with rationale and why alternatives are less suitable.
  2. Content guidelines -- title, message, button labels per Apple's tone and brevity rules.
  3. Dismiss behavior -- how the user dismisses and what happens (save, discard, cancel).
  4. Alternatives -- when the scenario might not need a modal at all (inline feedback, undo, progressive disclosure).

Questions to Ask

  1. What information or action does the presentation need?
  2. Blocking or non-blocking?
  3. Which platforms?
  4. How often does this appear?

Related Skills

  • hig-components-menus -- Buttons and toolbar items triggering presentations
  • hig-components-controls -- Input controls within sheets and popovers
  • hig-components-search -- Search and navigation within presented views
  • hig-patterns -- Modality, interruptions, user flow management
  • hig-foundations -- Color, typography, layout for presentation components

Built by Raintree Technology · More developer tools