{"id":77639,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:26.932Z","digest":"3fad3ef72a24b094f0e9436a8ffcebe9cc9aeb0c755580f70018d85832fd79ac","against":null,"payload":{"description":"Build or improve native macOS apps with SwiftUI and AppKit integrations, multiple windows, keyboard shortcuts, persistence and Xcode tests.","included_files":[],"name":"build-macos-app","skill_md_contents":"---\nname: build-macos-app\ndescription: Build or improve native macOS apps with SwiftUI and AppKit integrations, multiple windows, keyboard shortcuts, persistence and Xcode tests.\n---\n\n# Build Macos App\n\n1. Read `../../references/apple-native.md` and inspect target/architecture before editing.\n2. Respect macOS-specific patterns: menus, commands, focus, toolbar, sidebar/split view, multi-window behavior, document handling, drag-and-drop and native keyboard shortcuts. Do not merely enlarge an iPhone layout.\n3. Model autosave/retry, document identity, undo/redo, window restoration and resilient persistence when needed. Preserve existing data and filenames by default.\n4. Use SwiftUI for primary UI with AppKit where unavoidable. Handle accessibility, keyboard use, dark mode and dynamic resizing.\n5. Run xcodebuild/unit/UI tests on supported macOS host. On other platforms provide source and precise unverified test steps rather than a fake build pass.\n6. Packaging, signing and notarization require real Apple tooling/credentials and approval.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}