← ClaudeAtlas

macos-programmerlisted

macOS-specific development patterns, platform APIs, and decision frameworks. Use when developing Mac apps, macOS applications, Cocoa/AppKit code, or making SwiftUI vs AppKit decisions. Covers NSWindow management, NSDocument architecture, sandboxing, code signing, notarization, and macOS UI patterns. Applies to Mac Catalyst considerations.
Pyroxin/opinionated-claude-skills · ★ 5 · Data & Documents · score 74
Install: claude install-skill Pyroxin/opinionated-claude-skills
# macOS Programming <skill_scope skill="macos-programmer"> **Related skills:** - `swift-programmer` — Swift language fundamentals and Swift 6 concurrency - `software-engineer` — General software engineering principles and system architecture - `test-driven-development` — Testing philosophy and practices This skill covers macOS-specific development patterns, platform APIs, and decision frameworks. It applies when developing Mac apps, working with Cocoa/AppKit code, or making SwiftUI vs AppKit decisions. </skill_scope> ## Core Philosophy <core_philosophy> **Critical Reality (2024-2025):** SwiftUI for macOS is powerful but incomplete for production apps. Expert macOS developers must master BOTH SwiftUI and AppKit—SwiftUI for 70% of UI, AppKit for the 30% that makes professional apps professional. This hybrid approach is not a stopgap; it's the current production reality. **Platform Identity:** macOS is not iOS with a bigger screen. Multiple windows, menu bars, keyboard navigation, document-based architecture, and precise window management are first-class citizens. Respect macOS conventions; don't port iOS patterns blindly. </core_philosophy> ## SwiftUI vs AppKit: The Critical Decision Framework <swiftui_vs_appkit_decision> **The Ground Truth from Production Apps:** SwiftUI maturity varies dramatically by platform. The Ghostty Terminal case study demonstrates this: had to completely rip out SwiftUI's app/window lifecycle (+802/-239 lines) just to implement non-native full