apple-design-menus
Design Apple app command menus, context and edit menus, menu bars, Dock menus, and Home Screen quick actions, with discoverable commands and platform-correct organization.
SKILL.mdskills/design/apple-design-menus/SKILL.md
GitHubApple Menus and Commands
Apply the skill
Inventory commands by target, frequency, and current availability. Separate primary task controls from contextual shortcuts and global menu commands. Read the applicable menu references before deciding order, unavailable-item behavior, or shortcut presentation.
Keep standard command meanings and expected menu structure. Give contextual commands an accessible route outside the hidden menu. Label actions so their consequences are predictable and distinguish commands requiring additional input from commands that complete immediately.
Review menus in multiple selections and app states, including no selection. Do not apply one menu type’s availability rule to every menu: context menus, edit menus, and menu-bar menus have different expectations.
Topic references
Select the topic that matches the design decision; do not load this entire list by default.
Source use
These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.
Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.
The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.