skilld
All skills
raintree-technology avatar

/hig-components-menus

@71d5f4e
by Raintree Technologyraintree-technology/hig-doctor140 stars
9

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/raintree-technology/hig-doctor/hig-components-menus

This session only. Nothing lands on disk.

referencescontext-menus.md

≈615 tokens on demand. Your agent reads this file only when SKILL.md points to it.

<!-- hig-doctor:attribution -->

Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/context-menus. This file is a structured index of that content, snapshot 2025-02-02. Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

Context menus

  • The system-defined touch or pinch and hold gesture in visionOS, iOS, and iPadOS

  • Pressing the Control key while clicking a pointing device in macOS and iPadOS

  • Using a secondary click on a Magic Trackpad in macOS or iPadOS

Best practices

Prioritize relevancy when choosing items to include in a context menu.

Aim for a small number of menu items.

Support context menus consistently throughout your app.

Always make context menu items available in the main interface, too.

If you need to use submenus to manage a menu’s complexity, keep them to one level.

Hide unavailable menu items, don’t dim them.

Aim to place the most frequently used menu items where people are likely to encounter them first.

Show keyboard shortcuts in your app’s main menus, not in context menus.

Follow best practices for using separators.

In iOS, iPadOS, and visionOS, warn people about context menu items that can destroy data.

Content

Include a title in a context menu only if doing so clarifies the menu’s effect.

Represent menu item actions with familiar icons.

Platform considerations

iOS, iPadOS

Provide either a context menu or an edit menu for an item, but not both.

In iPadOS, consider using a context menu to let people create a new object in your app.

Prefer a graphical preview that clarifies the target of a context menu’s commands.

Ensure that your preview looks good as it animates.

visionOS

Consider using a context menu instead of a panel or inspector window to present frequently used functionality.

In general, avoid letting a context menu’s height exceed the height of the window.

<!-- hig-doctor:canonical-footer -->

For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/context-menus

Source: SKILL.md on GitHub

Third-party checks

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides Apple Human Interface Guidelines (HIG) reference materials for menu and button components. No security risks or harmful behaviors were detected.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 71d5f4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 weeks ago.

Activeupdated 8 months ago

Capability

version
1.0.0

README badge

README badge for raintree-technology/hig-doctor/hig-components-menus