← 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 · ★ 9 · AI & Automation · score 76
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> **Hybrid by default.** Production Mac apps commonly combine SwiftUI and AppKit: SwiftUI for most view content, AppKit where the platform's window, text, and event systems are exposed only there. Where the line falls varies by app; the case studies in `<swiftui_vs_appkit_decision>` show teams landing at different points, and each macOS release moves some formerly AppKit-only capability into SwiftUI (see `<recent_changes>`). Treat AppKit fallback as expected work rather than a failure of SwiftUI, and re-check the boundary when the deployment target moves. **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 T