Borrowing it
Nothing to install: this file belongs to chama-x/GroundRules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chama-x/GroundRules/master/.agents/archive/v3/skill_hig-doctor/skills/hig-components-menus/SKILL.mdgit clone --depth 1 https://github.com/chama-x/GroundRulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/chama-x/groundrules/hig-components-menus)<a href="https://agentmods.dev/skills/chama-x/groundrules/hig-components-menus"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/hig-components-menus.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00156 | $0.00979 |
| Opus 5 | $0.00078 | $0.00490 |
| Sonnet 5 | $0.00031 | $0.00196 |
| Haiku 4.5 | $0.00016 | $0.00098 |
Grade A, and why
hig-components-menus scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to hig-components-menus — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
-
Menus should be contextual and predictable. Standard items in standard locations. Follow platform conventions for ordering and grouping.
-
Use standard button styles. System-defined styles communicate affordance and maintain visual consistency. Prefer them over custom designs.
-
Toolbars for frequent actions. Most commonly used commands in the toolbar. Rarely used actions belong in menus.
-
Menu bar is the primary command interface on macOS. Every command reachable from the menu bar. Toolbars and context menus supplement, not replace.
-
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.
-
Pop-up buttons for mutually exclusive choices. Select exactly one option from a set.
-
Pull-down buttons for action lists. No current selection; they offer a set of commands.
-
Action buttons consolidate related actions behind a single icon in toolbars or title bars.
-
Disclosure controls for progressive disclosure. Show or hide additional content.
-
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 |
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/action-button.md 1.4 KB
- references/buttons.md 4.6 KB
- references/context-menus.md 2.4 KB
- references/disclosure-controls.md 1.2 KB
- references/dock-menus.md 872 B
- references/edit-menus.md 2.6 KB
- references/menus.md 3.1 KB
- references/pop-up-buttons.md 1.5 KB
- references/pull-down-buttons.md 1.7 KB
- references/the-menu-bar.md 3.0 KB
- references/toolbars.md 4.3 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 82 lines · 156 tokens per session scan A 8587f6eb574b
hig-components-menus is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 24d ago), licensed MIT. It adds 156 tokens to every session and 979 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hig-components-menus, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skin-creator
Create and apply a two-asset LobsterAI visual skin from the user's style description. Use only when the AI Skin Designer kit supplies the structured skinpack workflow marker; do not use for ordinary theme or image requests.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
b2b-desktop-design-system
Generate modern B2B desktop design system specs — tokens, layout, information hierarchy — for Near delivery POC.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
design-system
Use when a ticket needs a systematic token + component foundation for a frontend — the three-layer token architecture (primitive → semantic → component), component specs with full state coverage, or a recommendation for which design system a product should have. Invoke for "set up design tokens", "define the component…
brand
Use to establish or audit a product's brand so the factory's output looks intentional, not template — when a ticket asks to "create a brand", "define the design system / visual identity / palette / typography", or when delivered UI looks generic and needs a deliberate direction. Detects existing brand and extends it…