Agent skill

Hig Components Dialogs

by raintree-technology in raintree-technology/hig-doctor

Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.

MITAuto-check passedMobile

Install Hig Components Dialogs

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install raintree-technology/hig-doctor hig-components-dialogs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/raintree-technology/hig-doctor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hig-components-dialogs .claude/skills/hig-components-dialogs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
hig-components-dialogs
GitHub stars
143
Used in
5 other repos
Token cost
~1.1k tokens
SKILL.md length
417 words
Files
6 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.

  • Works in 10 steps: Alerts: sparingly, for critical… → Sheets: focused tasks that maintain… → Popovers: non-modal on iPad and Mac.… → …
  • The user says should I use an alert
  • SKILL.md covers Key Principles, Reference Index, Output Format and Questions to Ask, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Hig Components Dialogs is an agent skill from raintree-technology/hig-doctor. 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…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/action-sheets.md`, `references/alerts.md` and `references/digit-entry-views.md`).

It sits in Mobile, covering iOS development and Slides and decks. It works with macOS. The repository describes itself as: Apple HIG reference and cross-framework UI audit tooling for agents. The licence is MIT.

When your agent uses it

  • The user says should I use an alert
  • How do I show a confirmation dialog
  • Should I use a popover
  • My modals are annoying users

Example prompts

  • “should I use an alert or a sheet,”
  • “how do I show a confirmation dialog,”
  • “when should I use a popover,”
  • “/hig-components-dialogs”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Alerts: sparingly, for critical situations. Errors needing attention, destructive action confirmations, or information requiring…
  2. Sheets: focused tasks that maintain context. Slides in from the edge (or attaches to a window on macOS). Use for creating items, editing…
  3. Popovers: non-modal on iPad and Mac. Appear next to the trigger element, dismissed by tapping outside. For additional information…
  4. Action sheets: choosing among actions. Present when picking from multiple actions, especially if one is destructive. iPhone: slide up from…
  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"…
  7. Mark destructive actions clearly. Destructive button style (red text). Place destructive buttons where users are less likely to tap…
  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 3ec08f5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • raintree.technology

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hig Components Dialogs loads about 1.1k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 159 tokens; SKILL.md has 417 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~159
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from raintree-technology/hig-doctor at commit 3ec08f5, republished under its MIT licence (© raintree-technology). 417 words, ~1,053 tokens.

Download SKILL.mdSave it as .claude/skills/hig-components-dialogs/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
hig-components-dialogs
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.
version
1.0.0

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.

Show full SKILL.md (170 more words)Show less

Reference Index

ReferenceTopicKey content
alerts.mdAlertsButton ordering, title/message text, confirmation, destructive actions
action-sheets.mdAction sheetsMultiple actions, cancel option, destructive handling
popovers.mdPopoversNon-modal, dismiss on tap outside, iPad/Mac
sheets.mdSheetsModal task, context preservation
digit-entry-views.mdDigit entryPIN 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?
  • 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

© raintree-technology, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/hig-components-dialogs of raintree-technology/hig-doctor.

  • SKILL.md
  • references/action-sheets.md
  • references/alerts.md
  • references/digit-entry-views.md
  • references/popovers.md
  • references/sheets.md

Open the folder on GitHubat commit 3ec08f5

Used in 5 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in raintree-technology/hig-doctor, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Hig Components Dialogs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hig Components Dialogs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hig Components Dialogs this skillraintree-technology/hig-doctor1435 repos~1.1kAutomated safety check: PassMIT
macOS Auto Updatefayazara/macos-app-skills676—~1.8kAutomated safety check: PassNone
API Explorationsozercan/kaset2.4k—~454Automated safety check: PassMIT
Dev Loop Packagingsozercan/kaset2.4k—~388Automated safety check: PassMIT
App ItChristian-Katzmann/app-it216—~2.4kAutomated safety check: PassMIT
macOS App Designvaayne/mori303—~789Automated safety check: PassMIT

Similar skills

  • macOS Auto Update

    fayazara/macos-app-skills

    Add Sparkle auto-update support to a native macOS app. An agent skill from fayazara/macos-app-skills.

    676 GitHub stars~1.8k tokensUpdated 4 mo ago
    MobileAuto-check passed
  • API Exploration

    sozercan/kaset

    A skill your agent uses when a task needs a new or modified YouTube Music API call, response parser validation, authenticated endpoint investigation, or fixture capture; explore endpoints with swift…

    2.4k GitHub stars~454 tokensUpdated 5 days ago
    MobileAuto-check passed
  • Dev Loop Packaging

    sozercan/kaset

    A skill your agent uses when you need a fresh packaged .app bundle, a fast build-package-relaunch loop, or a packaged runtime repro for Kaset instead of a compile-only verification.

    2.4k GitHub stars~388 tokensUpdated 5 days ago
    MobileAuto-check passed
  • App It

    Christian-Katzmann/app-it

    Turn a local project or a hosted web app (including a published Claude Artifact URL) into a macOS Dock-launchable .app.

    216 GitHub stars~2.4k tokensUpdated 8 days ago
    MobileAuto-check passed
  • macOS App Design

    vaayne/mori

    A skill your agent uses when designing or building native macOS applications with SwiftUI or AppKit.

    303 GitHub stars~789 tokensUpdated 2 mo ago
    MobileAuto-check passed
  • macOS Tahoe APIs

    KartikLabhshetwar/better-shot

    Guide to macOS 26 Tahoe APIs and features. An agent skill from KartikLabhshetwar/better-shot.

    2.4k GitHub starsUsed in 1 repo~518 tokens
    MobileAuto-check passed

More from raintree-technology/hig-doctor

All 15 skills in this repo
  • Hig Project Context

    raintree-technology/hig-doctor

    Create or update a shared Apple design context document that other HIG skills use to tailor guidance.

    143 GitHub starsUsed in 5 repos~1.2k tokens
    Auto-check passed
  • Hig Components Content

    raintree-technology/hig-doctor

    Apple Human Interface Guidelines for content display components.

    143 GitHub starsUsed in 5 repos~1.3k tokens
    Auto-check passed
  • Hig Components Controls

    raintree-technology/hig-doctor

    Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards…

    143 GitHub starsUsed in 5 repos~1.3k tokens
    Auto-check passed
  • Hig Components Layout

    raintree-technology/hig-doctor

    Apple Human Interface Guidelines for layout and navigation components.

    143 GitHub starsUsed in 5 repos~1.6k tokens
    Auto-check passed
  • Hig Components Menus

    raintree-technology/hig-doctor

    Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure…

    143 GitHub starsUsed in 5 repos~1.1k tokens
    Auto-check passed
  • Hig Components Search

    raintree-technology/hig-doctor

    Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.

    143 GitHub starsUsed in 5 repos~828 tokens
    Auto-check passed

Works with

Categories

Questions about Hig Components Dialogs

What does Hig Components Dialogs do?

Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Hig Components Dialogs is an agent skill from raintree-technology/hig-doctor. Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.

When should I use Hig Components Dialogs?

Hig Components Dialogs fits situations like: the user says should I use an alert; how do I show a confirmation dialog; should I use a popover; my modals are annoying users.

How do I install Hig Components Dialogs in Claude Code?

Run `npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs -a claude-code`. Or copy the skill folder (skills/hig-components-dialogs in raintree-technology/hig-doctor) into .claude/skills/hig-components-dialogs in your project. Claude Code loads it when a task matches its description.

How do I install Hig Components Dialogs in Codex?

Run `npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs -a codex`. Or copy the skill folder (skills/hig-components-dialogs in raintree-technology/hig-doctor) into .agents/skills/hig-components-dialogs in your project. Codex loads it when a task matches its description.

Can I use Hig Components Dialogs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add raintree-technology/hig-doctor --skill hig-components-dialogs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hig-components-dialogs, .gemini/skills/hig-components-dialogs, .github/skills/hig-components-dialogs and .opencode/skills/hig-components-dialogs in your project.

What does Hig Components Dialogs need to run?

SKILL.md names no scripts, command-line tools or credentials: Hig Components Dialogs is instructions for the agent only.

Does Hig Components Dialogs access the network?

SKILL.md names 1 domain. As links in the text: raintree.technology. This is read from the text; nothing was executed.

Is Hig Components Dialogs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hig Components Dialogs use?

Hig Components Dialogs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hig Components Dialogs use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Hig Components Dialogs?

Skills that share tags, products or a category with Hig Components Dialogs: macOS Auto Update (fayazara/macos-app-skills, 676 stars), API Exploration (sozercan/kaset, 2.4k stars), Dev Loop Packaging (sozercan/kaset, 2.4k stars) and App It (Christian-Katzmann/app-it, 216 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hig Components Dialogs?

raintree-technology (a GitHub organization) maintains it in raintree-technology/hig-doctor, which has 143 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 11, 2026.

Source: raintree-technology/hig-doctor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.