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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
AGI Framework Integration
Adapted for @techwavedev/agi-agent-kit
Original source: antigravity-awesome-skills
Memory-First Protocol
Retrieve prior design decisions (color palettes, typography, spacing scales) to maintain visual consistency across sessions. Cache generated design tokens.
# Check for prior frontend/design context before starting
python3 execution/memory_manager.py auto --query "design system decisions and component patterns for Hig Components Dialogs"
Storing Results
After completing work, store frontend/design decisions for future sessions:
python3 execution/memory_manager.py store \
--content "Design system: adopted 8px grid, Inter font family, HSL color tokens with dark mode support" \
--type decision --project <project> \
--tags hig-components-dialogs frontend
Multi-Agent Collaboration
Share design decisions with backend agents (API contract changes) and QA agents (visual regression baselines).
python3 execution/cross_agent_context.py store \
--agent "<your-agent>" \
--action "Implemented UI components — new design system with accessibility compliance (WCAG 2.1 AA)" \
--project <project>
Design Memory Persistence
Store design system tokens and component decisions in Qdrant so any agent on any platform (Claude, Gemini, Cursor) can retrieve and apply consistent styling.
1---2name: hig-components-dialogs3description: Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.4---56# Apple HIG: Presentation Components78Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.910## Key Principles11121. **Alerts: sparingly, for critical situations.** Errors needing attention, destructive action confirmations, or information requiring acknowledgment. They interrupt flow and demand a response.13142. **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.15163. **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.17184. **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.19205. **Minimize interruptions.** Before reaching for a modal, consider inline presentation or making the action undoable instead.21226. **Concise, actionable alert text.** Short descriptive title. Brief message body if needed. Button labels should be specific verbs ("Delete", "Save"), not "OK".23247. **Mark destructive actions clearly.** Destructive button style (red text). Place destructive buttons where users are less likely to tap reflexively.25268. **Provide a cancel option** for alerts and action sheets with multiple actions. On action sheets, cancel appears at the bottom, separated.27289. **Digit entry: focused and accessible.** Appropriately sized input fields, automatic advancement between digits, support for paste and autofill.293010. **Adapt presentation to platform.** The same interaction may use different components on iPhone, iPad, Mac, and visionOS.3132## Reference Index3334| Reference | Topic | Key content |35|---|---|---|36| [alerts.md](references/alerts.md) | Alerts | Button ordering, title/message text, confirmation, destructive actions |37| [action-sheets.md](references/action-sheets.md) | Action sheets | Multiple actions, cancel option, destructive handling |38| [popovers.md](references/popovers.md) | Popovers | Non-modal, dismiss on tap outside, iPad/Mac |39| [sheets.md](references/sheets.md) | Sheets | Modal task, context preservation |40| [digit-entry-views.md](references/digit-entry-views.md) | Digit entry | PIN input, autofill, auto-advance |4142## Output Format43441. **Recommended presentation type with rationale** and why alternatives are less suitable.452. **Content guidelines** -- title, message, button labels per Apple's tone and brevity rules.463. **Dismiss behavior** -- how the user dismisses and what happens (save, discard, cancel).474. **Alternatives** -- when the scenario might not need a modal at all (inline feedback, undo, progressive disclosure).4849## Questions to Ask50511. What information or action does the presentation need?522. Blocking or non-blocking?533. Which platforms?544. How often does this appear?5556## Related Skills5758- **hig-components-menus** -- Buttons and toolbar items triggering presentations59- **hig-components-controls** -- Input controls within sheets and popovers60- **hig-components-search** -- Search and navigation within presented views61- **hig-patterns** -- Modality, interruptions, user flow management62- **hig-foundations** -- Color, typography, layout for presentation components6364---6566*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*6768## When to Use69This skill is applicable to execute the workflow or actions described in the overview.7071---7273<!-- AGI-INTEGRATION-START -->7475## AGI Framework Integration7677> **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)**78> Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills)7980### Memory-First Protocol8182Retrieve prior design decisions (color palettes, typography, spacing scales) to maintain visual consistency across sessions. Cache generated design tokens.8384```bash85# Check for prior frontend/design context before starting86python3 execution/memory_manager.py auto --query "design system decisions and component patterns for Hig Components Dialogs"87```8889### Storing Results9091After completing work, store frontend/design decisions for future sessions:9293```bash94python3 execution/memory_manager.py store \95 --content "Design system: adopted 8px grid, Inter font family, HSL color tokens with dark mode support" \96 --type decision --project <project> \97 --tags hig-components-dialogs frontend98```99100### Multi-Agent Collaboration101102Share design decisions with backend agents (API contract changes) and QA agents (visual regression baselines).103104```bash105python3 execution/cross_agent_context.py store \106 --agent "<your-agent>" \107 --action "Implemented UI components — new design system with accessibility compliance (WCAG 2.1 AA)" \108 --project <project>109```110111### Design Memory Persistence112113Store design system tokens and component decisions in Qdrant so any agent on any platform (Claude, Gemini, Cursor) can retrieve and apply consistent styling.114115<!-- AGI-INTEGRATION-END -->
techwavedev