Skip to main content
skill CX Codex

hig-components-dialogs — Claude Code skill: what it does & setup

Provides Apple Human Interface Guidelines for alerts, sheets, popovers, and digit entry views. Helps pick the right modal UI pattern across iOS, iPadOS, macOS, and visionOS.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs -a claude-code
Open on GitHub

What hig-components-dialogs does

This skill guides selection among presentation components: alerts, sheets, action sheets, and popovers. It questions whether you even need a modal. Modals interrupt flow and demand immediate responses. When possible, the skill suggests inline feedback or undo patterns instead of blocking dialogs.

The skill covers five reference components: alerts, action sheets, popovers, sheets, and digit entry views. For destructive actions, it insists on explicit verbs like "Delete" styled in red text. Generic "OK" labels are ruled out. Every output supplies a recommended component with rationale, copy guidelines, dismiss rules, and non-modal alternatives.

Before asking follow-up questions, the skill checks for .claude/apple-design-context.md. Without that file, Claude Code prompts you for platform details and blocking requirements. Component behavior changes significantly between iPhone, iPad, Mac, and visionOS.

What it helps with

  • choose between alerts, action sheets, popovers, and sheets per Apple HIG
  • write concise title and button labels for destructive confirmation dialogs
  • implement PIN or digit entry views with auto-advance and paste support
  • replace disruptive modal dialogs with inline feedback or undo actions

Example prompts for the agent

  • Should I use an alert or a sheet for this confirmation step?
  • How do I design a destructive action sheet for iOS?
  • When should I use a popover instead of a modal sheet on iPad?

How to install hig-components-dialogs

1Skills CLI (Vercel)

npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs -a claude-code

2Manually: put the files in place

~/.claude/skills/hig-components-dialogs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hig-components-dialogs/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hig-components-dialogs

How to install hig-components-dialogs in Claude Code?

Run npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs -a claude-code. This installs the skill files into your Claude Code environment.

What does hig-components-dialogs do?

It provides Apple HIG guidelines for alerts, action sheets, popovers, sheets, and digit entry views. It evaluates whether a modal is needed and outlines specific copy, button styles, and dismiss behaviors.

What is the purpose of apple-design-context.md?

The skill checks for .claude/apple-design-context.md before prompting you. If your project details are already saved there, Claude Code skips basic clarifying questions about target platforms and blocking requirements.

Source text

SKILL.md · MIT
---
name: hig-components-dialogs
version: 1.0.0
description: >-
  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.
---

# 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.

2. **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.

3. **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.

4. **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.

5. **Minimize interruptions.** Before reaching for a modal, consider inline presentation or making the action undoable instead.

6. **Concise, actionable alert text.** Short descriptive title. Brief message body if needed. Button labels should be specific verbs ("Delete", "Save"), not "OK".

7. **Mark destructive actions clearly.** Destructive button style (red text). Place destructive buttons where users are less likely to tap reflexively.

8. **Provide a cancel option** for alerts and action sheets with multiple actions. On action sheets, cancel appears at the bottom, separated.

9. **Digit entry: focused and accessible.** Appropriately sized input fields, automatic advancement between digits, support for paste and autofill.

10. **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](https://raintree.technology) · [More developer tools](https://raintree.technology)*

© raintree-technology · MIT · raintree-technology/hig-doctor

Similar skills

Everything for Design →

From the same set14

hig-components-layout Guides app navigation and layout architecture across Apple platforms based on the Human Interface Guidelines. CX Codex +1 684installs hig-patterns A skill with interaction patterns from Apple's Human Interface Guidelines: onboarding, loading, modality, notifications, search. Useful when you design UX for an Apple app. CX Codex +1 685installs hig-platforms Provides Apple Human Interface Guidelines for multi-platform design across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. Helpful when adapting an app to another Apple device. CX Codex +1 666installs hig-components-controls Applies Apple HIG principles to pickers, toggles, text fields, and inputs. Guides control selection, state behavior, and VoiceOver accessibility. CX Codex +1 655installs hig-components-menus Guides button and menu architecture across Apple platforms based on official Human Interface Guidelines. Helps choose proper controls and organize toolbars. CX Codex +1 643installs hig-components-content Provides Apple Human Interface Guidelines for content components like charts and collections. It helps choose standard controls across Apple platforms. CX Codex +1 641installs hig-components-status Provides Apple Human Interface Guidelines for progress indicators and status bars. Useful when building interfaces for iOS and watchOS. CX Codex +1 636installs hig-components-search Tells your agent how to design search, paging and breadcrumbs the Apple HIG way. Useful while you are still sketching navigation for an iOS or macOS app. CX Codex +1 634installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor