macos-design-guidelines
This skill distills Apple's Human Interface Guidelines into actionable rules for macOS development. Learn how to implement standard menu structures, keyboard shortcuts, resizable windows, fullscreen support, and toolbars that power users expect. Includes SwiftUI and AppKit code examples for every pattern.
macOS Design Guidelines helps you build native Mac apps following Apple's HIG with proper menus, windows, and keyboard controls.
AI-generated summary based on this skill's SKILL.md
Install
ehmo/platform-design-skills/macos
git clone https://github.com/ehmo/platform-design-skills
cp -r platform-design-skills/skills/macos ~/.claude/skills/macosFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to build Mac apps with SwiftUI following macOS design guidelines?
macos-design-guidelines teaches you to build native Mac apps using SwiftUI with proper menu bars, toolbars, and window management. The skill covers standard menu structures, keyboard shortcuts, resizable windows, and fullscreen support that power users expect. You'll find actionable SwiftUI code examples for every pattern, from basic window setup to advanced features like split-view support and document-based app architecture.
What are the best practices for Mac app window management?
macos-design-guidelines emphasizes proper window lifecycle, resizing behavior, and fullscreen/split-view support as core Mac app expectations. The skill teaches how to implement standard window controls, manage multiple windows, and ensure your app respects macOS window management conventions. Examples cover both SwiftUI and AppKit approaches to window state, restoration, and user preferences.
How do you implement keyboard navigation in a Mac application?
macos-design-guidelines provides comprehensive guidance on keyboard navigation and shortcuts for Mac applications. The skill covers focus management, keyboard event handling, standard macOS shortcuts (Cmd+Z for undo, Cmd+S for save), and accessibility-compliant navigation patterns. You'll learn to implement Full Keyboard Access support and ensure every UI element is reachable without a mouse.
What accessibility features must Mac apps include?
macos-design-guidelines ensures your app meets macOS accessibility standards including VoiceOver support, Full Keyboard Access, and sufficient color contrast. The skill teaches focus management for screen readers, semantic labeling, and testing with macOS accessibility tools. Proper accessibility also improves usability for all users through better keyboard navigation and visual clarity.
How do you design Mac UI with sidebars and system-native patterns?
macos-design-guidelines covers modern macOS UI design using sidebars, popovers, and system-native visual patterns that users recognize. The skill includes SwiftUI examples for sidebar navigation, toolbar customization, and context menus. You'll learn visual effects like vibrancy and materials that create the polished Mac aesthetic while maintaining consistency with Apple's design language.
Should you use AppKit or SwiftUI for macOS development?
macos-design-guidelines addresses the AppKit vs SwiftUI choice by showing both frameworks' strengths. SwiftUI excels for modern, declarative UI with built-in macOS support; AppKit provides deeper system integration and legacy compatibility. The skill teaches when each is appropriate and how to combine them—SwiftUI for new features, AppKit for specialized needs like advanced window management or Services menu integration.
SKILL.md
rendered from the published skill — quoted content, verbatim
macOS Human Interface Guidelines
Mac apps serve power users who expect deep keyboard control, persistent menu bars, resizable multi-window layouts, and tight system integration. These guidelines codify Apple's HIG into actionable rules with SwiftUI and AppKit examples.
1. Menu Bar (CRITICAL)
Every Mac app must have a menu bar. It is the primary discovery mechanism for commands. Users who cannot find a feature will look in the menu bar before anywhere else.
Rule 1.1 — Provide Standard Menus
Every app must include at minimum: App, File, Edit, View, Window, Help. Omit File only if the app is not document-based. Add app-specific menus between Edit and View or between View and Window.
```swift // SwiftUI — Standard menu structure @main struct MyApp: App { var body: some Scene {
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 4 files
skills/macos/AGENTS.md
skills/macos/SKILL.md
skills/macos/metadata.json
skills/macos/rules/_sections.md