agentleFS
CarlosZieglerCarlosZiegler/zietec-skills/skills/design/apple-design-menus/SKILL.md

apple-design-menus

Skill1 starsChanged 52 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep standard command meanings and expected menu structure.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  • Menus
  • Context menus
  • Edit menus
  • The menu bar
  • Dock menus
  • Home Screen quick actions

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.