Hig Components Menus logo

Hig Components Menus

Organization
raintree-technology
hig-components-menus

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.

Overview

Publisherraintree-technology
Repositoryhig-doctor
Skill namehig-components-menus
Stars
148
Forks
10
Bundled files
11
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 11 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by raintree-technology on GitHub. Read the source before you install it.

Installation

Install the Hig Components Menus AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-components-menus
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/raintree-technology/hig-doctor.git /tmp/hig-doctor
mkdir -p .claude/skills
cp -r /tmp/hig-doctor/skills/hig-components-menus .claude/skills/hig-components-menus
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hig Components Menus in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hig Components Menus on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hig Components Menus is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

ReferenceTopicKey content
menus.mdGeneral menu designItem ordering, grouping, shortcuts
context-menus.mdContext menusRight-click, long press, secondary actions
dock-menus.mdDock menusmacOS app-level actions, running state
edit-menus.mdEdit menusUndo, copy, paste, standard items
the-menu-bar.mdMenu barmacOS primary command interface, structure
toolbars.mdToolbarsFrequent actions, customization, placement
buttons.mdButtonsSystem styles, sizing, affordance
action-button.mdAction buttonGrouped secondary actions, toolbar use
pop-up-buttons.mdPop-up buttonsMutually exclusive choice selection
pull-down-buttons.mdPull-down buttonsAction lists, no current selection
disclosure-controls.mdDisclosure controlsProgressive 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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Hig Components Menus AI skill do?

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

Why use Hig Components Menus on TypingMind?

Because you install it once and use it with any model. Hig Components Menus is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hig Components Menus in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-components-menus. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Hig Components Menus?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hig Components Menus?

As many as you like. As long as a model supports skills, you can use Hig Components Menus with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hig Components Menus AI skill free?

Yes. It is published on GitHub by raintree-technology under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇