hig-doctor-audit
Audit interface source with HIG Doctor when the user asks to scan, lint, review, or remediate Swift, UIKit, AppKit, React, Vue,…
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 controls, and standard buttons. Use this skill when the user says "how should my
$ npx -y skills add raintree-technology/hig-doctor --skill hig-components-menus --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hig-components-menusContext preview
The summary Claude sees to decide when to auto-load this skill.
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 controls, and standard buttons. Use this skill when the user says "how should my
name: hig-components-menus version: 1.0.0 description: >- 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 controls, and standard buttons. Use this skill when the user says "how should my buttons look," "what goes in the menu bar," "should I use a context menu or action sheet," "how do I design a toolbar," or asks about button design, menu design, context menu, toolbar, menu bar, action button, pop-up button, pull-down button, disclosure control, dock menu, edit menu, or any menu/button component layout and behavior. Cross-references: hig-components-search, hig-components-controls, hig-components-dialogs.
Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
1. **Menus should be contextual and predictable.** Standard items in standard locations. Follow platform conventions for ordering and grouping.
2. **Use standard button styles.** System-defined styles communicate affordance and maintain visual consistency. Prefer them over custom designs.
3. **Toolbars for frequent actions.** Most commonly used commands in the toolbar. Rarely used actions belong in menus.
4. **Menu bar is the primary command interface on macOS.** Every command reachable from the menu bar. Toolbars and context menus supplement, not replace.
5. **Context menus for secondary actions.** Right-click or long-press, relevant to the item under the pointer. Never put a command only in a context menu.
6. **Pop-up buttons for mutually exclusive choices.** Select exactly one option from a set.
7. **Pull-down buttons for action lists.** No current selection; they offer a set of commands.
8. **Action buttons consolidate related actions** behind a single icon in toolbars or title bars.
9. **Disclosure controls for progressive disclosure.** Show or hide additional content.
10. **Dock menus: short and focused** on the most useful actions when the app is running.
| Reference | Topic | Key content | |---|---|---| | [menus.md](references/menus.md) | General menu design | Item ordering, grouping, shortcuts | | [context-menus.md](references/context-menus.md) | Context menus | Right-click, long press, secondary actions | | [dock-menus.md](references/dock-menus.md) | Dock menus | macOS app-level actions, running state | | [edit-menus.md](references/edit-menus.md) | Edit menus | Undo, copy, paste, standard items | | [the-menu-bar.md](references/the-menu-bar.md) | Menu bar | macOS primary command interface, structure | | [toolbars.md](references/toolbars.md) | Toolbars | Frequent actions, customization, placement | | [buttons.md](references/buttons.md) | Buttons | System styles, sizing, affordance | | [action-button.md](references/action-button.md) | Action button | Grouped secondary actions, toolbar use | | [pop-up-buttons.md](references/pop-up-buttons.md) | Pop-up buttons | Mutually exclusive choice selection | | [pull-down-buttons.md](references/pull-down-buttons.md) | Pull-down buttons | Action lists, no current selection | | [disclosure-controls.md](references/disclosure-controls.md) | Disclosure controls | Progressive disclosure, show/hide |
1. **Component recommendation** -- which menu or button type and why. 2. **Visual hierarchy** -- placement, sizing, grouping within the interface. 3. **Platform-specific behavior** across iOS, iPadOS, macOS, visionOS. 4. **Keyboard shortcuts** (macOS) -- standard and custom shortcuts for menu items and toolbar actions.
1. Which platforms? 2. Primary or secondary action? 3. How many actions need to be available? 4. macOS menu bar app?
---
*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
Active open-source project · MIT tooling with attributed Apple reference content HIG Doctor helps developers and coding agents find interface issues before release.
Audit interface source with HIG Doctor when the user asks to scan, lint, review, or remediate Swift, UIKit, AppKit, React, Vue,…
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about "charts component",…
Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo…
Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this…
Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about "sidebar", "split…
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. Use this skill…