macos-design-guidelines

Applies Apple Human Interface Guidelines rules to macOS SwiftUI and AppKit development.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/RavitejaKarra24/dotfiles --skill macos-design-guidelines-ravitejakarra24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: macos-design-guidelines
Source: https://github.com/RavitejaKarra24/dotfiles/tree/main/agents/.agents/skills/macos-design-guidelines
Command: npx skills add https://github.com/RavitejaKarra24/dotfiles --skill macos-design-guidelines-ravitejakarra24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a Mac app that feels native requires knowing dozens of Apple Human Interface Guidelines rules covering menu bars, windows, toolbars, keyboard shortcuts, and accessibility. This Skill codifies 62 HIG rules with SwiftUI and AppKit code examples so developers and reviewers can apply them consistently when building or auditing macOS apps. ## Core Features & Use Cases - 62 Categorized Rules: Eleven sections covering Menu Bar, Windows, Toolbars, Sidebars, Keyboard, Pointer, Notifications, System Integration, Visual Design, Popovers, and Accessibility, each tagged CRITICAL, HIGH, or MEDIUM priority. - SwiftUI and AppKit Code Examples: Every rule includes working code for both frameworks, from CommandGroup menus to NSWindow configuration and VoiceOver labels. - Anti-Pattern Guardrails: Explicit "never do" list blocking iOS patterns like hamburger menus, bottom tab bars, and floating action buttons on Mac. - Use Case: When porting an iOS app to Mac via Catalyst, use this Skill to audit the UI against the checklist and fix violations like missing menu bar commands, non-resizable windows, or hardcoded colors that break Dark Mode. ## Quick Start Review my SwiftUI Mac app's main window code against the macOS design guidelines and list any violations of the CRITICAL rules.

Frequently Asked Questions about macos-design-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a SwiftUI app feel native on macOS?

Follow the macOS Human Interface Guidelines: provide a full menu bar with standard menus, support resizable multi-window layouts, add keyboard shortcuts for every action, and use system fonts, semantic colors, and vibrancy materials. This Skill provides 62 rules with SwiftUI code examples for each area.

What keyboard shortcuts should a Mac app support?

Mac apps need standard shortcuts like Cmd+N, Cmd+O, Cmd+S, Cmd+Z, Cmd+W, and Cmd+Q, plus Cmd+letter shortcuts for every custom action. Esc must dismiss dialogs, Return activates the default button, and full Tab and arrow key navigation is required.

Does this work for both SwiftUI and AppKit?

Yes, every rule includes code examples for both SwiftUI and AppKit. SwiftUI examples use modifiers like .commands, .toolbar, and .searchable, while AppKit examples use NSMenu, NSWindow, NSToolbar, and NSVisualEffectView.

What iOS patterns should be avoided when porting to Mac with Catalyst?

Never use hamburger menus, bottom tab bars, or floating action buttons on Mac. Replace them with the menu bar, sidebars, and toolbar actions. Also avoid non-resizable windows, hardcoded colors that break Dark Mode, and omitting keyboard shortcuts.

Which macOS accessibility rules are mandatory?

Accessibility is marked CRITICAL: every interactive element needs a VoiceOver label, all actions must be keyboard reachable with no traps, and apps must respect Reduce Motion, Reduce Transparency, Bold Text, and Increase Contrast settings.