macos-app-designlisted
Design and build OpenAI-Codex-quality native macOS apps with the polish of Linear, Things 3, Granola, Notion Calendar, Arc Browser, Raycast, and Apple's own apps. Use this skill whenever the user is building, reviewing, or polishing a native Swift/SwiftUI Mac app — including AI coding tools, productivity apps, note-taking apps, design tools, dev tools, menu-bar utilities, or document-based apps. Targets macOS 14 (Sonoma) minimum and especially macOS 26 (Tahoe / Liquid Glass). Triggers on: macOS, Mac app, native Mac, SwiftUI Mac, AppKit, NSWindow, NSToolbar, NSStatusItem, NavigationSplitView, sidebar, toolbar, menu bar, MenuBarExtra, traffic lights, multi-window, document-based app, NSDocument, .commands, .keyboardShortcut, .onHover, .contextMenu, three-column layout, Inspector pattern, Liquid Glass macOS, Tahoe, command palette, Cmd-K, Dock badge, Sparkle, notarization, Developer ID, code editor, syntax highlighting, SF Mono, Stage Manager, Continuity, Spotlight, Quick Look, Apple Intelligence.
heyimjames/ios-design-skills · ★ 0 · Code & Development · score 75
Install: claude install-skill heyimjames/ios-design-skills
# macOS App Design — Design Engineering Skill
A taste guide for building macOS apps that feel like they were built by people who use Macs all day. Every value below is opinionated and specific — drawn from studying OpenAI's Codex app (the modern reference for AI-powered Mac apps), Linear's Mac client, Things 3, Granola, Raycast, Notion Calendar, Arc Browser, and Apple's own first-party apps.
This skill assumes a native Swift/SwiftUI Mac app, targeting macOS 14 (Sonoma) minimum and ideally macOS 26 (Tahoe — Liquid Glass). It pairs with the iOS skills in this marketplace — many polish principles transfer, but **Mac is its own platform with its own conventions**, and ignoring them is the single most common way Mac apps feel "off."
---
## Output format — required
When this skill is invoked to review macOS code or recommend changes, **always output recommendations as a markdown table** with three columns:
| Before | After | What this changes |
| --- | --- | --- |
| The current code, value, or approach (quote the user's actual code when possible) | The recommended replacement — **specific**, with exact values | One sentence on what the user will *see, feel, or experience* differently |
Three rules:
1. **Before** quotes the user's actual code where possible.
2. **After** is specific. Exact NSWindow sizes, exact keyboard shortcuts, exact toolbar item placements.
3. **What this changes** is *experiential or visual*, not abstract.
Output ONE table with multiple rows for multi-r