About
This skill provides Apple's Human Interface Guidelines for designing menus and button components, including menu bars, context menus, toolbars, and various button types. Use it when you need guidance on component layout, behavior, or choosing between UI elements like context menus versus action sheets. It offers specific design principles and cross-references related HIG skills for controls, search, and dialogs.
Quick Install
Claude Code
Recommendednpx skills add raintree-technology/claude-starter -a claude-code/plugin add https://github.com/raintree-technology/claude-startergit clone https://github.com/raintree-technology/claude-starter.git ~/.claude/skills/hig-components-menusCopy and paste this command in Claude Code to install this skill
Documentation
Apple HIG: Menus and Buttons
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
Key Principles
-
Menus should be contextual and predictable. Standard items in standard locations. Follow platform conventions for ordering and grouping.
-
Use standard button styles. System-defined styles communicate affordance and maintain visual consistency. Prefer them over custom designs.
-
Toolbars for frequent actions. Most commonly used commands in the toolbar. Rarely used actions belong in menus.
-
Menu bar is the primary command interface on macOS. Every command reachable from the menu bar. Toolbars and context menus supplement, not replace.
-
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.
-
Pop-up buttons for mutually exclusive choices. Select exactly one option from a set.
-
Pull-down buttons for action lists. No current selection; they offer a set of commands.
-
Action buttons consolidate related actions behind a single icon in toolbars or title bars.
-
Disclosure controls for progressive disclosure. Show or hide additional content.
-
Dock menus: short and focused on the most useful actions when the app is running.
Reference Index
| Reference | Topic | Key content |
|---|---|---|
| menus.md | General menu design | Item ordering, grouping, shortcuts |
| context-menus.md | Context menus | Right-click, long press, secondary actions |
| dock-menus.md | Dock menus | macOS app-level actions, running state |
| edit-menus.md | Edit menus | Undo, copy, paste, standard items |
| the-menu-bar.md | Menu bar | macOS primary command interface, structure |
| toolbars.md | Toolbars | Frequent actions, customization, placement |
| buttons.md | Buttons | System styles, sizing, affordance |
| action-button.md | Action button | Grouped secondary actions, toolbar use |
| pop-up-buttons.md | Pop-up buttons | Mutually exclusive choice selection |
| pull-down-buttons.md | Pull-down buttons | Action lists, no current selection |
| disclosure-controls.md | Disclosure controls | Progressive disclosure, show/hide |
Output Format
- Component recommendation -- which menu or button type and why.
- Visual hierarchy -- placement, sizing, grouping within the interface.
- Platform-specific behavior across iOS, iPadOS, macOS, visionOS.
- Keyboard shortcuts (macOS) -- standard and custom shortcuts for menu items and toolbar actions.
Questions to Ask
- Which platforms?
- Primary or secondary action?
- How many actions need to be available?
- macOS menu bar app?
Related Skills
- hig-components-search -- Search fields, page controls alongside toolbars and menus
- hig-components-controls -- Toggles, pickers, segmented controls complementing buttons
- hig-components-dialogs -- Alerts, sheets, popovers triggered by menu items or buttons
- hig-inputs -- Keyboard shortcuts and pointer interactions with menus and toolbars
Built by Raintree Technology · More developer tools
GitHub Repository
Frequently asked questions
What is the hig-components-menus skill?
hig-components-menus is a Claude Skill by raintree-technology. Skills package instructions and resources that Claude loads on demand, so Claude can perform hig-components-menus-related tasks without extra prompting.
How do I install hig-components-menus?
Use the install commands on this page: add hig-components-menus to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does hig-components-menus belong to?
hig-components-menus is in the Meta category, tagged design.
Is hig-components-menus free to use?
Yes. hig-components-menus is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Related Skills
This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.