hig-components-dialogs

Q: How do I install hig-components-dialogs?

Run npx skills add https://github.com/raintree-technology/hig-doctor --skill hig-components-dialogs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/hig-components-dialogs/ (personal) or .claude/skills/hig-components-dialogs/ (project).

by raintree-technologyDocs & Writing

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.

Installs: 654
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/raintree-technology/hig-doctor --skill hig-components-dialogs

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads hig-components-dialogs automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

Alerts: sparingly, for critical situations. Errors needing attention, destructive action confirmations, or information requiring acknowledgment. They interrupt flow and demand a response.
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.
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.
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.
Minimize interruptions. Before reaching for a modal, consider inline presentation or making the action undoable instead.
Concise, actionable alert text. Short descriptive title. Brief message body if needed. Button labels should be specific verbs ("Delete", "Save"), not "OK".
Mark destructive actions clearly. Destructive button style (red text). Place destructive buttons where users are less likely to tap reflexively.
Provide a cancel option for alerts and action sheets with multiple actions. On action sheets, cancel appears at the bottom, separated.
Digit entry: focused and accessible. Appropriately sized input fields, automatic advancement between digits, support for paste and autofill.
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	Alerts	Button ordering, title/message text, confirmation, destructive actions
action-sheets.md	Action sheets	Multiple actions, cancel option, destructive handling
popovers.md	Popovers	Non-modal, dismiss on tap outside, iPad/Mac
sheets.md	Sheets	Modal task, context preservation
digit-entry-views.md	Digit entry	PIN input, autofill, auto-advance

Output Format

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

Questions to Ask

What information or action does the presentation need?
Blocking or non-blocking?
Which platforms?
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

FAQ

What does the hig-components-dialogs skill do?

How do I install hig-components-dialogs?

Run npx skills add https://github.com/raintree-technology/hig-doctor --skill hig-components-dialogs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/hig-components-dialogs/ (personal) or .claude/skills/hig-components-dialogs/ (project).

Which AI agents can use hig-components-dialogs?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is hig-components-dialogs safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains hig-components-dialogs?

It is published by raintree-technology in raintree-technology/hig-doctor. It has 654 recorded installs.