Index of every page on this site: llms.txt
All skills
raintree-technology avatar

/hig-components-menus

@a0f1e4e
Run it yourself

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.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈180 tokens for metadata: the name and description. ≈897 when used: this file. ≈6.8k more on demand in 11 files.

Description uses 9.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈720 characters, or 9.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  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 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

  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.

Questions to Ask

  1. Which platforms?
  2. Primary or secondary action?
  3. How many actions need to be available?
  4. 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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

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

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub 3 weeks ago.

Activeupdated 9 months ago
version
1.0.0

README badge

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